Deploy Django app
A production Django application with PostgreSQL, collected static assets and durable media outside the container.
Run an admin-backed product or content application while keeping relational data and uploaded files across releases.
Build plan
- Run manage.py check --deploy with production settings and replace runserver with a production WSGI or ASGI server.
- Create managed PostgreSQL, collect static assets into the image and run the existing migrations at release startup.
- Keep uploaded media in S3-compatible storage over HTTPS and add a lightweight GET /health route.
Resources and values
1 ServicePostgreSQLObject storage for mediaDATABASE_URLSECRET_KEYALLOWED_HOSTSStorage credentials when neededThe application filesystem is temporary. collectstatic output may ship in the image, but user uploads cannot stay in MEDIA_ROOT.
Ask your coding agent
Prepare this Django repository for aidrop without changing its data model. Add a production Dockerfile, run manage.py check --deploy, collect static assets into the image and start a production WSGI or ASGI server on 0.0.0.0:8000 instead of runserver. Create managed PostgreSQL and adapt DATABASES to its DATABASE_URL. Read SECRET_KEY and allowed hosts from runtime values, use .aidrop.cloud for the first host rule and never use DEBUG=True. Add GET /health. If users upload media, configure S3-compatible storage over HTTPS; never write durable media to MEDIA_ROOT. Run existing migrations, deploy and verify the public address and /admin.
Put Django app online
Connect your coding agent, paste the quickstart and keep the build, runtime and public address in one aidrop Project.
7 days free · No credit card required