Refine deployment process

[xmedr]

Recently used this cookiecutter to deploy an app to heroku, and here are some findings for things to consider or sections to adjust:

• Had some trouble getting the build command working for the first time. So IIRC I had to specify that it should grab from main (instead of default master) and adjust it to something like: docker build github.com/datamade/cookiecutter-django-app#main -t cookiecutter:latest
• There were some small linting adjustments that needed to be made. Check out this commit for specifics.
• pytest needs to be added to requirements.txt
• Since the test run depends on having an image published to ghcr, the repo's initial commit to main should contain the cookiecutter's output.
• The 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.

[hancush]

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 main and triggering the publish package job via the Actions UI so the image that the tests and deployments depend on is created! Also making the package public (because our Heroku approach doesn't support building from private images).

[xmedr]

Agreed, sounds good. Some more things to adjust:

• Add gunicorn to the requirements
• A CSRF_TRUSTED_ORIGINS = ["https://*.herokuapp.com", "http://localhost:8000"] needs to go into settings
• Should adjust this line to include an argument is_default_site=True to the get_or_create.

[hancush]

Oh yeah, for Wagtail, ALLOWED_HOSTS also needs to include localhost:8000 for previews to work when editing pages.