ShippedDjango hosting
on Shipped.
Your Django app already has the foundations. Give its views, models, and admin a production home with the services they need.
Run Django with production settings
Deploy your application using an appropriate WSGI or ASGI server and production configuration. Keep secret keys outside source, disable debug behavior, and configure the hosts your app serves. Shipped provides the service address and HTTPS while Django remains responsible for application security and request handling.
Separate records, assets, and uploads
Connect your models to PostgreSQL and keep user uploads in persistent object storage. Treat collected static assets as part of your release rather than mixing them with customer files. This keeps the data people create independent of the application image that changes when you deploy code.
Release models and code with care
Run migrations as a deliberate part of a release and check the new behavior in staging. Background workers can handle email batches, imports, and document generation outside request handling. Use logs to investigate failures, and remember that restoring an app release does not reverse a database migration.
A little more detail
Questions about Django?
Can I use the Django development server in production?
Use a production WSGI or ASGI server instead. Django’s deployment documentation also covers settings, static files, and checks to perform before exposing an application publicly.
Do media uploads belong in the Django image?
No. Uploaded files must survive deployments and process replacement. Store them in persistent storage and keep the application configured to access that storage.
From your workspace to the web