src/docs/markdown/quick-starts/railway.md
Deploying Caddy on Railway is an easy, no-fuss way to deploy a custom Caddy build with plugins.
Prerequisites:
Go to our Download page and select any plugins you need, then click the purple "Deploy on Railway" button at the top.
<details> <summary>Or, configure the template manually</summary>Alternatively, if you want to configure the Railway template yourself, here is how to do it.
Go to the template on Railway:
<a href="https://railway.com/deploy/caddy?referralCode=YOPtw9&utm_medium=integration&utm_source=template&utm_campaign=generic"></a>
and add any plugins you need by clicking "Configure":
Then paste the plugins into the CADDY_PLUGINS variable, separated by spaces:
Click Deploy, then after the deployment finishes, you can try it out by clicking the link here:
You should see a welcome page showing that your new server is working!
Next, you can customize your deployment to serve your own site or proxy to another Railway service.
To serve your own website, or to change the config, simply "eject" our template into your own repository:
From your own repository, you can:
www folder.Simply commit the changes and push, then you can redeploy on Railway.
If you want to change the plugins in your Caddy build, all you have to do is edit the CADDY_PLUGINS variable and redeploy:
Railway terminates TLS for you, so you should write your Caddy config as if it is being proxied to (because it is). Hence, if you use hosts in your Caddyfile site addresses, you should use auto_https off in your global options. Caddy is not edge-facing with our template.
Environment variables you can set in your Railway project that this template may use:
| Name | Description | Default | Example(s) |
|---|---|---|---|
CADDY_PLUGINS | Space-separated list of Caddy plugins | | github.com/caddy-dns/cloudflare github.com/mholt/caddy-ratelimit |