Django hosting · Vallic Cloud
Django hosting · Vallic Cloud
Django hosting with migrations, static files and workers handled.
Django on machines no other customer shares, deployed from Git and served by Gunicorn: migrations once the release is live, static files collected in the build, uploads kept between releases, and PostgreSQL or MariaDB beside it.
On Vallic Cloud
What runs your Django site
You choose
Runtime
Database one of
You can add
Cache
Reverse proxy
Search
Time series
Background work
The default, unless vallic.yaml names another version.
Done for you
Scheduled
Runs python manage.py clearsessions every night at 03:00, without a crontab of yours.
Caches
Rebuilds them from the console, a button rather than a shell.
Kept between releases
media and private, so a deploy never loses what the site wrote.
Why here
The parts of Django that surround the code.
Migrations after the release is live
python manage.py migrate runs on the machine as a deploy step, before the health check asks. With on_failure: rollback, a migration that fails puts the previous release back.
Static files collected in the build
collectstatic runs in the build, which can write, and WhiteNoise serves the result from the release.
Settings from the environment
One settings module reads the database, the cache, ALLOWED_HOSTS and SECRET_KEY from the environment. Nothing secret is committed, and off the platform it does nothing.
Uploads outlive every release
MEDIA_ROOT is kept outside the release and is in every backup, so a deploy never loses a file.
Celery, supervised
Workers run in your application’s own image and release, kept alive and restarted on every deploy. Celery beat runs inside the worker.
Support from people who build applications
Our team builds and runs web applications for a living, and a ticket reaches them.
Moving a Django project here.
Add a vallic.yaml and the settings module from the handbook’s Django page, include it at the end of settings.py, import the database with vallic db import, and deploy.
Rather we did it? Our team moves applications as part of what it does.
Questions
Which database does Django use?
PostgreSQL or MariaDB. The first deploy takes the one the manifest names, and after the first release the database is fixed.
Are expired sessions cleared?
Yes. clearsessions runs every night at 03:00 unless vallic.yaml declares cron of its own.
Do you charge per request or per visit?
No. Machines are billed by the month, and traffic past what a machine includes by the terabyte.
Where can it run?
In any of the platform’s datacentres. The configurator shows each one’s machines and prices before you sign up.
