Make python buildpack easier to use for beginners - Githubissues

ehmatthes / heroku-buildpack-python

A demonstration version of the official Heroku buildpack for Python apps, showing how Django deployment can be further simplified.

https://ehmatthes.com/blog/simplified_heroku/

MIT License

16 stars 2 forks source link

Make python buildpack easier to use for beginners #1

Closed ehmatthes closed 3 years ago

ehmatthes commented 4 years ago

Heroku is much easier for beginning Django developers to deploy to than a VPS such as Digital Ocean or Linode. But there's still a fair bit of configuration that has to be done between having a project that runs on your local machine and one that runs on Heroku.

This project aims to simplify the deployment process as much as possible, while doing things, as much as possible, in a standardized Heroku way. The process should be easy to override as people learn more about custom deployments.

ehmatthes commented 4 years ago

Areas to simplify:

[x] Add a check for AUTOCONFIGURE_ALL, and put all of this code in that block for now.
[x] Create a Procfile if there is not one present.
- works in f0e71f8, but project name is hardcoded.
[x] Make git push heroku master not fail, then work through details, ie db. #4
[x] Don't require a runtime.txt. (I think this is already the case?) #3
[x] Configure other settings, such as ALLOWED_HOSTS. #6
[x] Configure the database.
- [x] Includes installing required packages if they're not listed in requirements.txt.
[x] Configure static files automatically, beyond just running collectstatic. #7
- [x] Set DISABLE_COLLECTSTATIC=1 while working on other aspects of deployment.
- [x] Includes installing required packages if they're not listed in requirements.txt.

End goal is only these steps need to be done:

make heroku account
install heroku cli
pip freeze > requirements.txt
set up git, commit
run heroku create
push to heroku

ehmatthes commented 4 years ago

Notes

Ideally this happens when a config var, or series of config vars are set, ie AUTO_CONFIGURE.
Should this be a pre-compile hook instead?
Look at $3, ENV_DIR.
ALLOWED_HOSTS = ['*'] for now, should be changed to heroku host. Set to .herokuapp.com, good enough for now. #6
What would this look like for non-requirements.txt projects? (Finished, #16)
It's quite fine if this doesn't work for all cases; it's meant for initial simple deployments, although should continue working for many moderate size projects.
Add more explicit comments around autoconfigured parts of settings.py.

ehmatthes commented 4 years ago

Try it with a demo project.

ehmatthes commented 4 years ago

This issue is finished for now, for initial demonstration purposes. But I'll leave this one open, because if this goes anywhere it still contains some next steps.

ehmatthes commented 3 years ago

All of this has been addressed, or documented elsewhere.