- Add caveat about automatic changes to settings.py and git conflict#1640
- Add caveat about automatic changes to settings.py and git conflict#1640kjcole wants to merge 2 commits intoDjangoGirls:masterfrom
Conversation
|
@hjwp Should |
I'm not at PA any more, but you could open an issue at https://github.com/pythonanywhere/helper_scripts/issues/ ? |
I've now filed pythonanywhere/helper_scripts#27 |
|
According to pythonanywhere/helper_scripts#27 (comment), the PythonAnywhere's Can we close this thus without merging? Or should we add instructions on how to make sure that indeed no modification occurred? (E.g. |
Because I missed the leading "." before "pythonanywhere.com" in settings.py my
ALLOWED_HOSTSread: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.pyhad 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.