-
Notifications
You must be signed in to change notification settings - Fork 0
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
Refine deployment process #9
Comments
Probably also a good idea to add a note to the usage section indicating that the cookiecutter output should be added to GitHub as one initial commit to |
Agreed, sounds good. Some more things to adjust:
|
Oh yeah, for Wagtail, |
I used this approach to derive trusted CSRF origins from allowed hosts for NOAH: https://github.com/datamade/tpc-ihs-noah-map/blob/e46e67e97957890e0cf57cd370b580ccf1738984/noah_map/settings.py#L35C1-L44C40 |
Also recently deployed an app generated w/ cookie cutter to Heroku (my first time working with Heroku), here are my notes: Notes
|
Also just noting that "noah_map" is hardcoded here instead of the cookie cutter module name |
Recently used this cookiecutter to deploy an app to heroku, and here are some findings for things to consider or sections to adjust:
docker build github.com/datamade/cookiecutter-django-app#main -t cookiecutter:latest
pytest
needs to be added torequirements.txt
clear_cache
management command needs to be added. Check out its implementation in la-metro-councilmatic for a solution.More may come as I finish the heroku deployment.
The text was updated successfully, but these errors were encountered: