Deploy Django in six steps
- 01
Push your Django project to a GitHub repository.
- 02
Sign in to Rimbra, choose New project and import the repository. Rimbra asks GitHub for access to the repositories you pick.
- 03
Rimbra sees a requirements.txt or pyproject.toml and a manage.py and runs pip install, then Django on PORT. Set your own start command, such as gunicorn, in Settings. Change the root directory or the commands in Settings if your project needs it.
- 04
Paste your .env into Variables. Every line becomes a variable, available on the next deploy.
- 05
Deploy. The build log streams line by line, and your app goes live at your-project.rimbra.live (or .xyz or .click, your choice) over HTTPS.
- 06
Optional: buy or connect a domain, and Rimbra points it at your app with HTTPS issued automatically.
What your app needs
One rule for servers: listen on the port in the PORT environment variable. Rimbra sets it and routes your address to it.
gunicorn mysite.wsgi --bind 0.0.0.0:$PORTDjango on Rimbra
- Add your Rimbra address and your domain to ALLOWED_HOSTS.
- Connect a PostgreSQL or MySQL database and DATABASE_URL is set for you, ready for SQLAlchemy, psycopg or dj-database-url.
- Put SECRET_KEY and DEBUG=False in the project’s variables.
Read the full list of detected frameworks and default commands in the frameworks docs.
Questions
Can I run migrations on Rimbra?
Yes. Add python manage.py migrate to the build command, or run it in the start command before gunicorn.
Can I host a Django app for free?
Yes. Rimbra’s Free plan needs no card and includes 4 projects, 1 database, 200 build minutes and 50 GB of bandwidth a month, with a free HTTPS address for each project.
Does every push redeploy my Django app?
Yes. Every push to your production branch builds a new version. It goes live only when it answers, so visitors never see a broken release, and you can roll back to an earlier build instantly.