← Templates · Applications
ME
MediaCMS
Verified5 services
MediaCMS, the open-source video and media CMS — upload, transcode, and publish video from your own branded portal.
| Runs | 5 services |
|---|---|
| Stack | mediacmsmediacms-workermediacms-beatmediacms-dbmediacms-redis |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Yes, deployed end to end by the Railyard team |
Why deploy on Railyard
Railyard provisions all 5 services in this stack together — mediacms, mediacms-worker, mediacms-beat, mediacms-db, mediacms-redis — wired to reach each other over the private network, on a server you already pay for.
Deploying MediaCMS is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- A branded video portal for an organization's internal or public media library
- Self-hosted video hosting with transcoding split into its own worker process
Good to know
- Postgres and Redis are wired up automatically across web, the Celery worker and beat scheduler
- SECRET_KEY is generated and shared across web, worker and beat — without it, MediaCMS's own local_settings.py falls back to a hardcoded Django secret key baked into every copy of this image, which would let anyone forge signed cookies or password-reset tokens on any deployment that left it unset
- ADMIN_PASSWORD is generated so the admin login is visible in the dashboard — left unset, MediaCMS's own prestart.sh invents a random one and only prints it once to the release log
- Transcoding runs in the Celery worker — give it real CPU if you expect concurrent uploads
- Uploaded media lives on a volume shared between web and the worker so both see the same files