-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some corrections and an additions #15
base: master
Are you sure you want to change the base?
Conversation
Setup the API via Docker: Added, that the Server is running after the first sudo docker-compose up --build and rewrote the following information for a better "flowing" readability. Setting up the database seeder for local development: Corrected the path from config/docker/* to config/*, and optimized the following sentence a bit.
. | ||
|
||
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? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
. You see no more changes in your terminal-window? | |
. This may take a while, depending on your hardware and your internet connection. |
|
||
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? | ||
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). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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). |
|
||
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`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AndreasAusKiel thanks! Here are some suggestions how to improve the docs. Code is usually better than text (it's easier to copy+paste 😉)
Setup the API via Docker:
Added, that the Server is running after the first sudo docker-compose up --build and rewrote the following information for a better "flowing" readability.
Setting up the database seeder for local development:
Corrected the path from config/docker/* to config/*, and optimized the following sentence a bit.