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

ops: attach vault-dash to proxy-net and document vd1 route

Browse Source
This commit is contained in:
Bu5hm4nn
2026-03-23 23:35:47 +01:00
parent ed6daf6d47
commit 46ce81d2d6
2 changed files with 23 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/DEVOPS_DEPLOY_PROMPT.md
View File

@@ -78,11 +78,19 @@ env:
4. **Configure Docker on the VPS**:
- Ensure Docker and Docker Compose are installed
- 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
5. **Verify network connectivity**:
5. **Publish VPN route through Caddy**:
- Add `http://vd1.uncloud.vpn` 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`
- Reload Caddy and verify `http://vd1.uncloud.vpn/health` over VPN
6. **Verify network connectivity**:
- Forgejo runner must be able to reach the VPS via SSH
- VPS must be able to pull images from the registry
## Instructions for the DevOps Agent
When setting up the deployment: