forked from continuwuation/continuwuity
.well-known env var in example composes now point to `example.com:443`, and are turned on by default for Caddy labels and the Traefik configs. For the Caddyfile example, they're left uncommented. Added small bulletpoint on how to use this env var. Consistencize all the .well-known comments inside these composes. I don't want to overly fix the example composes and get it wrong, so this small change should be enough. Split-domain deployments are fully outsourced to the Delegation page now, and some changes are also made there to be more comprehensive.
55 lines
1.6 KiB
YAML
55 lines
1.6 KiB
YAML
services:
|
|
caddy:
|
|
image: docker.io/caddy:latest
|
|
ports:
|
|
- 80:80
|
|
- 443:443
|
|
- 8448:8448
|
|
networks:
|
|
- caddy
|
|
volumes:
|
|
- ./data:/data
|
|
restart: unless-stopped
|
|
configs:
|
|
- source: Caddyfile
|
|
target: /etc/caddy/Caddyfile
|
|
|
|
homeserver:
|
|
image: forgejo.ellis.link/continuwuation/continuwuity:latest
|
|
restart: unless-stopped
|
|
command: /sbin/conduwuit
|
|
volumes:
|
|
- db:/var/lib/continuwuity
|
|
- ./continuwuity-resolv.conf:/etc/resolv.conf # use custom resolvers rather than Docker's
|
|
#- ./continuwuity.toml:/etc/continuwuity.toml
|
|
environment:
|
|
CONTINUWUITY_SERVER_NAME: example.com
|
|
CONTINUWUITY_DATABASE_PATH: /var/lib/continuwuity
|
|
CONTINUWUITY_ADDRESS: 0.0.0.0
|
|
CONTINUWUITY_PORT: 8008
|
|
#CONTINUWUITY_CONFIG: '/etc/continuwuity.toml' # Uncomment if you mapped config toml above
|
|
|
|
## (Optional) Serve .well-known files to tell others to reach Continuwuity on port :443
|
|
## If you do this, remove all routes to port :8448 from the compose and Caddyfile
|
|
# CONTINUWUITY_WELL_KNOWN: |
|
|
# {
|
|
# client=https://example.com,
|
|
# server=example.com:443
|
|
# }
|
|
|
|
|
|
networks:
|
|
- caddy
|
|
|
|
networks:
|
|
caddy:
|
|
|
|
volumes:
|
|
db:
|
|
|
|
configs:
|
|
dynamic.yml:
|
|
content: |
|
|
https://example.com, https://example.com:8448 {
|
|
reverse_proxy http://homeserver:8008
|
|
}
|