Quick Start: Deploying to Heroku
Heroku is in the process of eliminating its free tier, but it will still be around as a hosting platform. As long as Heroku maintains a deployment process that can be scripted,
simple_deploy will maintain support for Heroku.
Deployment to Heroku can be fully automated, but the configuration-only approach is recommended. This allows you to review the changes that are made to your project before committing them and making the initial push. The fully automated approach configures your project, commits these changes, and pushes the project to Heroku's servers.
Deployment to Heroku requires three things:
- You must be using Git to track your project.
- You need to have a
requirements.txtfile at the root of your project, or use Poetry or Pipenv to manage your project's dependencies.
- The Heroku CLI must be installed on your system.
django-simple-deploy, and add
INSTALLED_APPS in settings.py:
Now create a new Heroku app using the CLI, and run
simple_deploy to configure your app:
At this point, you should review the changes that were made to your project. Running
git status will show you which files were modified, and which new files were created.
If you want to continue with the deployment process, commit these change, push your project to Heroku, and run migrations against the deployed project. When deployment is complete, use the
open command to see the deployed version of your project:
You can find a record of the deployment process in
simple_deploy_logs. It contains most of the output you saw when running
If you want, you can automate this entire process. This involves just three steps:
You should see a bunch of output as Heroku resources are created for you, your project is configured for deployment, and
simple_deploy pushes your project to Heroku's servers. When everything's complete, your project should open in a new browser tab.
Pushing further changes
After the initial deployment, you're almost certainly going to make further changes to your project. When you've updated your project and it works locally, you can commit these changes and push your project again, without using
If deployment does not work, please feel free to open an issue. Please share the OS you're using locally, and the specific error message or unexpected behavior you saw. If the project you're deploying is hosted in a public repository, please share that as well.
Please remember that
django-simple-deploy is in a preliminary state. That said, I'd love to know the specific issues people are running into so we can reach a 1.0 state in a reasonable time frame.