- Add caveat about automatic changes to settings.py and git conflict #1640
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because I missed the leading "." before "pythonanywhere.com" in settings.py my
ALLOWED_HOSTS
read:This meant that the testing on the local development machine worked, but the deployed copy did not. I quickly realized the mistake, but since
pa_autoconfigure_django.py
had changed the "production" copy ofsettings.py
, it was out of sync with the both my development machine and the hosted git repository.Missing the leading "." seems like a potentially common mistake. So maybe that's where the tutorial should change, calling people's attention to that, instead.