- HTML 98.8%
- Dockerfile 1.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Signed S3 requests and the hold's presigned URLs failed with 403 Invalid signature through hold-s3.hexlab.foo while succeeding on the tailnet name: Garage saw a Host different from the one signed. The Tailscale Service passes the original Host through, so the rewrite is simply dropped. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> |
||
| image | ||
| observability | ||
| .gitignore | ||
| Caddyfile | ||
| docker-compose.yml | ||
| nginx.conf | ||
| README.md | ||
tranquil-pds on pds (at.hexlab.foo)
Live config for the Vultr VM that serves the ATProto PDS at at.hexlab.foo
and, per the pi-argo hold plan, will front the cluster's ATCR hold at
hold.hexlab.foo / hold-s3.hexlab.foo. This directory is the deployment:
/opt/tranquil-pds on the VM is a checkout of this repo.
What runs
docker-compose.yml: tranquil-pds (port 3000, image built locally from
image/), db (Postgres 18), caddy (80/443, config in Caddyfile),
prometheus (127.0.0.1:9090, config in observability/).
Not in git
config.toml: PDS config with JWT/DPoP/master secrets and the DB URL..env:POSTGRES_PASSWORD, read by compose for thedbservice.certs/: old certbot material from before Caddy took over TLS.src/: upstream source,https://tangled.org/tranquil.farm/tranquil-pds.gitateb034cb. Re-clone and check out that commit to rebuild; bump the ref here when upgrading.image/tranquil-pds: the binary built fromsrc/and copied into the image.nginx.confis committed but unused (pre-Caddy); compose does not reference it.
Operate
cd /opt/tranquil-pds
docker compose config # render, proves .env is picked up
docker compose up -d # apply compose changes
docker compose up -d --force-recreate caddy # after a Caddyfile edit (see below)
Caddy issues certs itself (HTTP-01; on-demand for *.at.hexlab.foo, gated by
the :5555 handle check). New hostnames get their own site block.
Caddyfile changes need a container recreate, not caddy reload. The
compose file bind-mounts the single file ./Caddyfile; git pull replaces
it with a new inode, and the running container keeps the old one, so a
reload reports "config is unchanged". Recreating the container (a few
seconds of downtime for the PDS) re-binds the file. Learned 2026-10-13.