WBS-7.9: target snapshot admin deploy host runner
This commit is contained in:
@@ -70,6 +70,32 @@ bash /volume1/projects/data_feed/tools/run_snapshot_admin_synology.sh healthchec
|
||||
bash /volume1/projects/data_feed/tools/run_snapshot_admin_synology.sh restart
|
||||
```
|
||||
|
||||
## 4b. Gitea Actions runner label
|
||||
|
||||
Use a unique host label so the deployment job is not mixed with generic self-hosted work.
|
||||
|
||||
- Runner label: `snapshot-admin-host`
|
||||
- Registration example:
|
||||
|
||||
```bash
|
||||
REG_TOKEN="<runner-registration-token>" \
|
||||
GITEA_URL="http://192.168.123.100:8418" \
|
||||
RUNNER_LABEL="snapshot-admin-host" \
|
||||
bash tools/re_register_act_runner_synology.sh
|
||||
```
|
||||
|
||||
- Workflow selector:
|
||||
|
||||
```yaml
|
||||
runs-on: [self-hosted, snapshot-admin-host]
|
||||
```
|
||||
|
||||
## 4c. Queue handling
|
||||
|
||||
- If the deploy workflow stays queued, it usually means the host runner is busy.
|
||||
- Check the job currently holding the runner before re-dispatching.
|
||||
- Do not keep dispatching deploy runs back-to-back. The workflow already uses `concurrency` to cancel in-progress duplicates.
|
||||
|
||||
## 5. Reverse proxy
|
||||
|
||||
- DSM path: `Control Panel > Login Portal > Advanced > Reverse Proxy`
|
||||
|
||||
Reference in New Issue
Block a user