bu5hm4nn/vault-dash
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update production URL to lombard.uncloud.tech

Browse Source
This commit is contained in:
Bu5hm4nn
2026-03-25 09:24:54 +01:00
parent c7c8654be7
commit 7932148b73
2 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/DEVOPS_DEPLOY_PROMPT.md
View File

@@ -80,11 +80,11 @@ env:
- The deploy script will pull the container image from the registry - The deploy script will pull the container image from the registry
- Ensure the shared external Docker network `proxy-net` exists so Caddy can reverse proxy the deployment by container name - Ensure the shared external Docker network `proxy-net` exists so Caddy can reverse proxy the deployment by container name
5. **Publish VPN route through Caddy**: 5. **Publish public route through Caddy**:
- Add `http://vd1.uncloud.vpn` to `/opt/caddy/Caddyfile` - Add `lombard.uncloud.tech` to `/opt/caddy/Caddyfile`
- Restrict access with the existing `@not-vpn` matcher for `10.100.0.0/24`
- Reverse proxy to `vault-dash:8000` on `proxy-net` - Reverse proxy to `vault-dash:8000` on `proxy-net`
- Reload Caddy and verify `http://vd1.uncloud.vpn/health` over VPN - Reload Caddy and verify `https://lombard.uncloud.tech/health`
- Remove the retired `vd1.uncloud.vpn` route if it still exists
6. **Verify network connectivity**: 6. **Verify network connectivity**:
- Forgejo runner must be able to reach the VPS via SSH - Forgejo runner must be able to reach the VPS via SSH

8
docs/ROADMAP.md
View File

@@ -291,13 +291,13 @@ DATA-001 (Price Feed)
**Dependencies:** DATA-001, PORT-001 **Dependencies:** DATA-001, PORT-001
### OPS-001: Caddy Route for Production Dashboard [P1, S] **[depends: deploy-stable]** ### OPS-001: Caddy Route for Production Dashboard [P1, S] **[depends: deploy-stable]**
**As a** VPN user, **I want** to reach the deployed dashboard at `vd1.uncloud.vpn` **so that** I can access it without SSH port forwarding. **As a** user, **I want** to reach the deployed dashboard at `lombard.uncloud.tech` **so that** I can access it directly over HTTPS.
**Acceptance Criteria:** **Acceptance Criteria:**
- Caddy route proxies `vd1.uncloud.vpn` to local deployment container - Caddy route proxies `lombard.uncloud.tech` to the deployment container
- Route works over the VPN only - HTTPS works with a valid certificate
- Health check succeeds through Caddy - Health check succeeds through Caddy
- Deployment docs include the route and where it lives - Deployment docs include the route and note that `vd1.uncloud.vpn` was retired
**Dependencies:** stable deployed app on VPS **Dependencies:** stable deployed app on VPS