b6e223291a
- docker-compose.yml: Forgejo service on hiy-net, configured via env vars - postgres-init/01-forgejo.sql: creates forgejo user + database on first Postgres init - .env.example: document FORGEJO_DB_PASSWORD and FORGEJO_DOMAIN Routing: add FORGEJO_DOMAIN as an app in HIY pointing to forgejo:3000, or add a Caddyfile block manually. https://claude.ai/code/session_01FKCW3FDjNFj6jve4niMFXH
17 lines
644 B
Text
17 lines
644 B
Text
# Your domain — apps will be served at <name>.yourdomain.com
|
|
DOMAIN_SUFFIX=yourdomain.com
|
|
|
|
# Optional: email for Let's Encrypt expiry notices.
|
|
# If you want this, uncomment the `email` line in proxy/Caddyfile instead.
|
|
|
|
# Dashboard login credentials (required in production).
|
|
HIY_ADMIN_USER=admin
|
|
HIY_ADMIN_PASS=changeme
|
|
|
|
# Postgres admin password — used by the shared cluster.
|
|
# App schemas get their own scoped users; this password never leaves the server.
|
|
POSTGRES_PASSWORD=changeme
|
|
|
|
# Forgejo (optional — only needed if you add the forgejo service to docker-compose.yml).
|
|
FORGEJO_DB_PASSWORD=changeme
|
|
FORGEJO_DOMAIN=git.yourdomain.com
|