Render, Railway and Fly
These platforms build the Dockerfile, give Bunker a persistent disk at /data, and terminate HTTPS for you. Bunker detects the public URL from the platform’s variables (RENDER_EXTERNAL_URL, RAILWAY_PUBLIC_DOMAIN, FLY_APP_NAME), so usually you set nothing.
Render
Section titled “Render”render.yaml defines one Docker web service:
- plan
starter(persistent disks need a paid instance), - a 5 GB disk
bunker-dataat/data, - health check
/healthz, BUNKER_SETUP_CODEgenerated for you (find it in Environment),BUNKER_RUN_UID=0, because Render’s disks are owned by root.
When you add a custom domain, set BUNKER_URL to it.
Railway
Section titled “Railway”Deploy on Railway: the template builds the Dockerfile with a volume at /data, sets BUNKER_RUN_UID=0 and generates a BUNKER_SETUP_CODE (in the service’s Variables). Open the generated domain and go to /setup.
Or by hand, from your fork:
- New project → Deploy from GitHub repo, pick your fork of Bunker.
railway.jsonsets the Dockerfile builder and the health check. - Variables: add
BUNKER_RUN_UID=0(Railway volumes are owned by root). - Settings → Volumes: add a volume mounted at
/data. - Settings → Networking → Generate domain, then open it. Create your account on the setup page (the setup code is in the deploy logs).
Fly.io
Section titled “Fly.io”fly launch --from https://github.com/kucukkanat/bunker --copy-configfly logs # setup URL and codefly.toml creates a 1 GB volume bunker_data at /data, keeps one machine always running (auto_stop_machines = "off", min_machines_running = 1), forces HTTPS and checks /healthz. Grow the volume with fly volumes extend.
Platforms that lose data
Section titled “Platforms that lose data”DigitalOcean App Platform, Heroku and Google Cloud Run have no persistent block disks. Their buttons are fine for a demo, but the database resets. For DigitalOcean, use a Droplet with the Linux installer instead.