scriptoriumadmin/fabro
1
0
Fork 0
mirror of https://github.com/fabro-sh/fabro.git synced 2026-08-28 05:27:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 6

chore: move Caddyfile into docker/

Browse source 
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Bryan Helmkamp 2026-04-27 11:23:02 -07:00
parent 1bdb0be3a8
commit e78539b2a3
No known key found for this signature in database
3 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docker-compose.prod.yaml
View file

@ -8,7 +8,7 @@ services:
- "80:80"
- "443:443"
volumes:
- ./Caddyfile:/etc/caddy/Caddyfile
- ./docker/Caddyfile:/etc/caddy/Caddyfile
- caddy_data:/data
- caddy_config:/config
depends_on:

0
Caddyfile → docker/Caddyfile
View file

2
docs/public/administration/deploy-digital-ocean.mdx
View file

@ -11,7 +11,7 @@ DigitalOcean is a good fit for self-hosting Fabro on a Droplet — a plain Linux
- `docker-compose.yaml` pulls the pre-built image from GHCR and declares a named volume for `/storage`
- `docker-compose.prod.yaml` adds a [Caddy](https://caddyserver.com) sidecar that terminates TLS and auto-provisions Let's Encrypt certificates
- `Caddyfile` reverse-proxies HTTPS traffic to the Fabro server
- `docker/Caddyfile` reverse-proxies HTTPS traffic to the Fabro server
<Note>
**Why not App Platform?** DigitalOcean App Platform has no persistent volumes — it is designed for stateless workloads that offload state to managed Postgres or Spaces. Fabro writes runs, checkpoints, sessions, and JWT keys to `/storage`, so a Droplet (or any VPS) is the right fit. If you prefer Kubernetes, DOKS works too — that path is not documented here.