1 Commits

Author SHA1 Message Date
3927274e25 test: recipe-create-pr skill smoke test 2026-05-18 15:53:31 +00:00
3 changed files with 7 additions and 12 deletions

View File

@ -1,6 +1,6 @@
{
on_demand_tls {
ask http://pds:3000/tls-check
ask http://app:3000/tls-check
}
}
@ -8,5 +8,5 @@
tls {
on_demand
}
reverse_proxy pds:3000
reverse_proxy app:3000
}

View File

@ -150,3 +150,5 @@ as implemented by bluesky, although other pds implementations exist such as [coc
# ❃
recipe maintained by @notplants
<!-- test commit for /recipe-create-pr skill (2026-05-18T15:53:31Z) -->

View File

@ -3,16 +3,9 @@ version: "3.8"
services:
app:
image: ghcr.io/bluesky-social/pds:0.4.219
image: ghcr.io/bluesky-social/pds:0.4
networks:
# Unique alias so the caddy sidecar resolves THIS stack's PDS, not a foreign service. On a
# shared host the default service name `app` is aliased by every co-located stack on the
# `proxy` overlay; caddy (attached to both `proxy` and `internal`) otherwise resolves bare
# `app` to another stack's endpoint, so its on-demand-TLS `ask` to the PDS is refused and the
# cert is never issued (HTTPS dead). `pds` exists only on `internal`, so it resolves correctly.
internal:
aliases:
- pds
- internal
environment:
- PDS_HOSTNAME=${DOMAIN}
- PDS_DATA_DIRECTORY=/pds
@ -43,7 +36,7 @@ services:
max_attempts: 5
labels:
- "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT:-120}"
- "coop-cloud.${STACK_NAME}.version=0.3.0+v0.4.219"
- "coop-cloud.${STACK_NAME}.version=0.2.0+v0.4"
- "backupbot.backup=true"
healthcheck:
test: ["CMD", "wget", "-q", "--spider", "http://localhost:3000/xrpc/_health"]