Expose staging port to reverse proxy
Validate and deploy staging / validate (push) Successful in 17s
Validate and deploy staging / deploy (push) Successful in 23s

This commit is contained in:
JB
2026-07-26 10:42:01 -04:00
parent f5eb2fd663
commit 75faef50b8
2 changed files with 6 additions and 3 deletions
+1 -1
View File
@@ -16,7 +16,7 @@ services:
TDR_AVATAR_STORAGE_PATH: /app/data/avatars TDR_AVATAR_STORAGE_PATH: /app/data/avatars
TDR_GAME_ICON_STORAGE_PATH: /app/data/game-icons TDR_GAME_ICON_STORAGE_PATH: /app/data/game-icons
ports: ports:
- "127.0.0.1:${SHD_STAGE_PORT:-5569}:3000" - "0.0.0.0:${SHD_STAGE_PORT:-5569}:3000"
volumes: volumes:
- shd_stage_data:/app/data - shd_stage_data:/app/data
healthcheck: healthcheck:
+5 -2
View File
@@ -25,7 +25,7 @@ database.
Staging defaults to: Staging defaults to:
- Public origin: `https://stage.shd.build` - Public origin: `https://stage.shd.build`
- Reverse-proxy upstream: `http://127.0.0.1:5569` - Reverse-proxy upstream: host port `5569`
- Database: `/app/data/shd-build-staging.db` - Database: `/app/data/shd-build-staging.db`
- Passkey relying-party ID: `shd.build` - Passkey relying-party ID: `shd.build`
- Adapter canonical origin: `https://stage.shd.build` - Adapter canonical origin: `https://stage.shd.build`
@@ -41,7 +41,10 @@ npm run env:encrypt:staging
Add `https://stage.shd.build/auth/discord/callback` to the Discord application's Add `https://stage.shd.build/auth/discord/callback` to the Discord application's
allowed OAuth redirect URIs. Point the staging DNS record at the deployment allowed OAuth redirect URIs. Point the staging DNS record at the deployment
host and configure the host's TLS reverse proxy to forward host and configure the host's TLS reverse proxy to forward
`stage.shd.build` to `127.0.0.1:5569`. `stage.shd.build` to port `5569` on the staging host. Docker publishes this
port on the host interfaces so a containerized reverse proxy or tunnel can
reach it; firewall the port to trusted LAN/tunnel sources when the host is
reachable from other networks.
The deployment decrypts `.env.staging` on the trusted staging runner into a The deployment decrypts `.env.staging` on the trusted staging runner into a
mode-`0600` runtime file. The decryption key is held by Gitea Actions, not mode-`0600` runtime file. The decryption key is held by Gitea Actions, not