
Deploy Dagu Workflows
Dagu YAML workflows on a cron scheduler with login and persistent history
Dagu
Just deployed
/var/lib/dagu
Deploy and Host Dagu Workflows
Dagu is a workflow engine and cron scheduler with a web UI. You write workflows as YAML DAGs of shell steps, and one Dagu process serves the UI and REST API, runs the scheduler and executes the steps. This template runs the official Dagu 2.27.0 image with a generated admin login and a volume that keeps your DAGs and their run history.
About Hosting Dagu Workflows
The template deploys one Dagu service with a 5,000 MB volume at /var/lib/dagu. Sign in as admin with the generated DAGU_AUTH_BUILTIN_INITIAL_ADMIN_PASSWORD from the service's Variables tab; Dagu creates that account on the first boot and closes its setup page; keep the variable set. Dagu's built-in login protects the UI, the API and the MCP endpoint. DAG definitions, run history, logs, step outputs, users and keys are written to the volume, so scheduled workflows and their history survive restarts and redeploys.
Why Deploy Dagu Workflows on Railway
Railway gives the UI HTTPS on a public domain, generates the admin password and keeps /var/lib/dagu on a persistent volume. The start command makes Railway's root-owned volume writable for Dagu's unprivileged user, refuses to start without authentication or with a weak password, and runs the unchanged upstream entrypoint. The image is pinned by digest, so every deploy runs the same build.
Common Use Cases
- Replace crontab entries with scheduled workflows that keep logs and history.
- Run data and ETL jobs as steps with dependencies, retries and timeouts.
- Trigger maintenance scripts from webhooks or the REST API.
- Give a small team a UI to start, retry and inspect batch jobs.
Dependencies for Dagu Workflows Hosting
- Outbound internet access for steps that call APIs, clone repositories or download tools.
- Any databases or services your workflows connect to.
Deployment Dependencies
Template Content