From 51475fc2e8a6b7a663c65f16c8bce56ba0eee32f Mon Sep 17 00:00:00 2001 From: Johannes Reppin Date: Wed, 23 Aug 2023 17:51:31 +0200 Subject: [PATCH] swagger endpoint not at explorer-next anymore --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c086f063d..1c329f0a9 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ or the SciCat team at ESS. 3. Add *.env* file to project root folder. See [Environment variables](#environment-variables). 4. *Optional* Add *functionalAccounts.json* file to project root folder. If not set up, the functional accounts in [functionalAccounts.json.example](/functionalAccounts.json.example) will be created automatically. 5. `npm run start:dev` -6. Go to http://localhost:3000/explorer-next to get an overview of available endpoints and database schemas. +6. Go to http://localhost:3000/explorer to get an overview of available endpoints and database schemas. 7. To be able to run the e2e tests with the same setup as in the Github actions you will need to run `npm run prepare:local` and after that run `npm run start:dev`. This will start all needed containers and copy some configuration to the right place. ## Develop in a container using the docker-compose.dev file @@ -37,7 +37,7 @@ or the SciCat team at ESS. 4. *Optional* change the container env variables 5. Attach to the container 6. `npm run start:dev` -7. Go to http://localhost:3000/explorer-next to get an overview of available endpoints and database schemas. +7. Go to http://localhost:3000/explorer to get an overview of available endpoints and database schemas. ## Test the app