-
Notifications
You must be signed in to change notification settings - Fork 40
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
Swap the order between running and initial setup on README.md #136
Comments
And localhost:8000 must to show a "successfully" screen, not a redirect to a external site. |
adorilson
added a commit
to adorilson/perfil-politico
that referenced
this issue
Aug 29, 2020
…kfn-brasil#136) This change was made in a online split, in pair-programming with Debora Atanes and Julianay Raiol.
adorilson
added a commit
to adorilson/perfil-politico
that referenced
this issue
Aug 29, 2020
sergiomario
added a commit
that referenced
this issue
Aug 29, 2020
doc: Swap the order between running and initial setup on README.md (#136)
Fixed by: 80d3f39 \o/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think in
README.md
the order of running and initial setup should be swapped.When
$ docker-compose up
is runned first the API is not made available atlocalhost:8000
, so I had to run$ docker-compose run django ./manage.py migrate
and after that run$ docker-compose up
.Talking with other people in the chat during the sprint, they had a similar issue.
The text was updated successfully, but these errors were encountered: