melabidi/carmanagement
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Update production registry pull over VPN
Build & Deploy / Build & Push Docker Image (push) Successful in 2m53s
Details
Test / Type Check (all packages) (push) Successful in 54s
Details
Build & Deploy / Deploy to VPS (push) Successful in 4s
Details
Test / API Unit Tests (push) Successful in 46s
Details
Test / Homepage Unit Tests (push) Successful in 43s
Details
Test / Storefront Unit Tests (push) Successful in 40s
Details
Test / Admin Unit Tests (push) Successful in 41s
Details
Test / Dashboard Unit Tests (push) Successful in 42s
Details
Test / API Integration Tests (push) Successful in 58s
Details

Browse Source 
Configure production defaults to pull images directly from the VPN registry at 10.0.0.4, with the VPS reachable at 10.0.0.1, and disable archive handoff by default.
This commit is contained in:
root
2026-07-02 11:36:35 -04:00
parent 2993dd5b57
commit 0394f0ea2a
5 changed files with 17 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
production/README.md
+7 -2
View File
@@ -42,16 +42,21 @@ If Docker needs to log in before pulling the app image, also set:
- `REGISTRY_USER`
- `REGISTRY_PASSWORD`
For the current VPN-reachable image registry, use:
For the current VPN-reachable image registry, use direct pulls from the VPS.
The registry is `10.0.0.4`, and the VPS WireGuard address is `10.0.0.1`.
```env
APP_IMAGE=10.0.0.4/melabidi/carmanagement
REGISTRY_HOST=10.0.0.4
REGISTRY_USER=melabidi
IMAGE_ARCHIVE_DIR=
IMAGE_ARCHIVE_REQUIRED=false
```
## VPN Container Image Handoff
If the registry is only reachable inside a VPN container, use the shared archive folder:
This fallback is only needed if the VPS cannot reach `10.0.0.4` directly. If the
registry is only reachable inside a VPN container, use the shared archive folder:
```env
IMAGE_ARCHIVE_DIR=/opt/docker-image-transfer