heroku-django-template icon indicating copy to clipboard operation
heroku-django-template copied to clipboard

A Django 2.0 base template featuring all recommended best practices for deployment on Heroku and local development.

Results 17 heroku-django-template issues
Sort by recently updated
recently updated
newest added

I see this project has been inactive for a long time, since April 2018 to be exact. Is this project active? I find it strange that I have to search...

-- Updated the comments and links to reflect moving to Django 3 (#103) -- Added dj-database-url packages to Pipfile to prevent module missing error when deploying -- Tested deploy to...

Or maybe have a separate repo for Django 3.0 template.

The latest psycopg2 v2.8 is giving me the following error when used as `pipenv install psycopg2` writing manifest file 'pip-egg-info/psycopg2.egg-info/SOURCES.txt'", " Error: b'You need to install postgresql-server-dev-NN for building a...

I think there's no need to specify `python_version` in `Pipfile`. The template works for newer Python versions as well. We can't specify multiple Python versions in `Pipfile`, but we can...

Looks like `dj_database_url` was not defined as a requirement.

As pipenv uses `.venv` directory if `PIPENV_VENV_IN_PROJECT` is set to 1, It would be better if default `.gitignore` ignores `.venv` folder.

Added django requirements file for seamless heroku deployment

Is there a reason why 'whitenoise.middleware.WhiteNoiseMiddleware', is ot included in MIDDLEWARE in settings.py? https://devcenter.heroku.com/articles/django-assets

Currently the whitenoise middleware gets included twice, because you are manually adding it into `settings.py` and calling `django_heroku.settings` without passing `staticfiles=False` (and therefore it gets added an other time by...