@@ -33,13 +33,13 @@ Trying it locally, we used the following commands to spin up a local Typesense s
3333
3434``` sh
3535mkdir /tmp/typesense-data
36- docker run -p 8108:8108 -v/tmp/data:/data typesense/typesense:0.21 .0 \
36+ docker run -p 8108:8108 -v/tmp/data:/data typesense/typesense:29 .0 \
3737 --data-dir /data --api-key=< temp-admin-api-key> --enable-cors
3838```
3939
4040To check that the server is running, we can open a browser at ` /health ` and we get back 200 OK with ` ok: true ` .
4141
42- The Typesense server has a [ REST API] ( https://typesense.org/docs/0.21. 0/api ) which can be used to manage the indexes you create.
42+ The Typesense server has a [ REST API] ( https://typesense.org/docs/29. 0/api/ ) which can be used to manage the indexes you create.
4343Or if you use their cloud offering, you can use their web dashboard to monitor and manage your index data.
4444
4545## Populating the index
@@ -265,7 +265,7 @@ cp ./search-server/typesense-server/Dockerfile ${GITHUB_WORKSPACE}/typesense-dat
265265cp ./search-server/typesense-scraper/typesense-scraper-config.json typesense-scraper-config.json
266266envsubst < " ./search-server/typesense-scraper/typesense-scraper.env" > " typesense-scraper-updated.env"
267267docker run -d -p 8108:8108 -v ${GITHUB_WORKSPACE} /typesense-data/data:/data \
268- typesense/typesense:0.21 .0 --data-dir /data --api-key=${TYPESENSE_API_KEY} --enable-cors &
268+ typesense/typesense:29 .0 --data-dir /data --api-key=${TYPESENSE_API_KEY} --enable-cors &
269269# wait for typesense initialization
270270sleep 5
271271docker run -i --env-file typesense-scraper-updated.env \
@@ -275,7 +275,7 @@ docker run -i --env-file typesense-scraper-updated.env \
275275Our ` Dockerfile ` then takes this data from the ` data ` folder during build.
276276
277277``` Dockerfile
278- FROM typesense/typesense:0.21 .0
278+ FROM typesense/typesense:29 .0
279279
280280COPY ./data /data
281281```
0 commit comments