Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions server-api/installation.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,9 +26,8 @@ Determine now the installed version, running
```bash
$ sudo docker-compose up --build
```
.

Now, your API should be running at [http://localhost:3030](http://localhost:3030) and you can see some contributions at [http://localhost:3030/contributions](http://localhost:3030/contributions).
. You see no more changes in your terminal-window?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
. You see no more changes in your terminal-window?
. This may take a while, depending on your hardware and your internet connection.

Congratulations: Your server is now running at [http://localhost:3030](http://localhost:3030) which you can load in your browser. Some contributions wait for you at [http://localhost:3030/contributions](http://localhost:3030/contributions).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Congratulations: Your server is now running at [http://localhost:3030](http://localhost:3030) which you can load in your browser. Some contributions wait for you at [http://localhost:3030/contributions](http://localhost:3030/contributions).
After a while, your server is running at [http://localhost:3030](http://localhost:3030) which you can load in your browser. Some contributions wait for you at [http://localhost:3030/contributions](http://localhost:3030/contributions).


For debugging you can run:

Expand All @@ -40,9 +39,9 @@ And debug your app with [Chrome Dev Tools](chrome://inspect).

### Setting up the database seeder for local development

Change configuration in `config/docker/local-development.json` or `config/docker/local.json` and rerun `docker-compose up --build`.
Change the configuration in `config/local-development.json` or `config/local.json` and rerun `docker-compose up --build`.

If both the files do no exist create a `config/local.json` and copy the content of `config/local.example.json` and rerun `docker-compose up --build`.
If both files do no exist, create a `config/local.json` , copy the content of `config/local.example.json` into it and rerun `docker-compose up --build`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If both files do no exist, create a `config/local.json` , copy the content of `config/local.example.json` into it and rerun `docker-compose up --build`.
If both files do not exist, run `cp config/local.example.json config/local.json` and rerun `docker-compose up --build`.
You can learn more about the purpose of these configuration files and the order how they are loaded in the wiki of `node-config`:


Reference : https://github.com/lorenwest/node-config/wiki/Configuration-Files

Expand Down