benya/rmm-openwrt
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

build: publish tunnel with server releases

Browse Source
This commit is contained in:
benya
2026-07-23 00:56:13 +03:00
parent 49d2debce6
commit a7ce37f1f8
6 changed files with 37 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
RELEASES.md
+10 -2
View File
@@ -7,14 +7,22 @@ Versioning.
Tags use `server-vMAJOR.MINOR.PATCH`, for example `server-v0.8.0`.
A server release contains the Go API, web interface, database migrations and deployment
files. The GitHub Actions server workflow tests the server and publishes:
A server release contains the Go API, web interface, database migrations and the coupled
SSH reverse-tunnel service. The GitHub Actions server workflow tests the server and
publishes two images with the same version:
```text
ghcr.io/benya9669/openwrt-rmm-server:0.8.0
ghcr.io/benya9669/openwrt-rmm-server:latest
ghcr.io/benya9669/openwrt-rmm-tunnel:0.8.0
ghcr.io/benya9669/openwrt-rmm-tunnel:latest
```
The tunnel remains a separate container for isolation, but shares the server release line
because its SSH policy and port-forwarding behavior form part of the server-side protocol.
Introduce independent `tunnel-v*` releases only if the tunnel later gains a separate API
and lifecycle.
Increment `MAJOR` for incompatible API or migration requirements, `MINOR` for compatible
features, and `PATCH` for compatible fixes. Database backups remain mandatory before a
production upgrade even when the release is marked compatible.