Detect a settings module as Django project type #15
Comments
Thanks for the feedback. This isn't the first time someone's asked us to support this. We'll keep it in mind. Luckily, it is recognized as a regular Python application, and will work properly if you configure it. You'll just have to add a few lines to get the database info from the environment in your settings. |
Ahh, yes...I logged it and then decided to start hacking for a solution. Thanks for the tip and for including the relevant info in an environment variable. For others who may come across this, the workaround is to add the following to the settings file being used:
|
Closed
podshumok
pushed a commit
to podshumok/heroku-buildpack-python
that referenced
this issue
Dec 19, 2012
Add version to the sample package.json shown in README.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a project with the following structure (following the recent advice of BDFL @jacobian, http://www.slideshare.net/jacobian/the-best-and-worst-of-django slide 51)
Unfortunately, Heroku doesn't detect this as a Django project due to the fact that a settings.py file does not exist.
The text was updated successfully, but these errors were encountered: