Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AndreasAusKiel
Copy link
Contributor

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.

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?
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.


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).
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).


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`:

Copy link
Contributor

@roschaefer roschaefer left a 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 😉)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants