Beyond a proof of concept

[ehmatthes]

The initial goal of this project was to provide a proof of concept that all initial deployment work could be done on Heroku's end, and require no local changes. To that end I have taken some shortcuts, such as setting ALLOWED_HOSTS = ['*'] (this has been addressed now).

As each of these is addressed in a more robust way, this moves closer to becoming a reliable real-world buildpack, not just a proof of concept. This issue is meant to keep track of issues that need to be addressed and questions that need to be answered in order to move beyond the proof of concept stage.

[ehmatthes]

• [ ] Building projects that use Pipenv: Right now Heroku-only requirements such as gunicorn are added to the [packages] section, and Pipfile.lock is deleted so it will be regenerated during the build. Is this a reasonable approach, or should the process of adding new requirements be handled differently?
• [ ] Develop a full set of env vars to control the auto-configuration process. Keep the AUTOCONFIGURE_ALL flag, but add others that allow disabling any individual step of the process, ie DISABLE_AUTOCONFIGURE_DB.
• [ ] Is there a way to automate the handling of media files?