Keep socket listener active during deployment
This commit is contained in:
@@ -169,6 +169,13 @@ systemctl daemon-reload
|
||||
systemctl restart uce.service
|
||||
```
|
||||
|
||||
When `uce.socket` is active, restart only `uce.service` (or use
|
||||
`scripts/systemd/manage-uce-service.sh restart`). The socket unit must retain
|
||||
ownership of the FastCGI listener while workers change. Restarting
|
||||
`uce.socket` alongside the service removes that listener briefly and can expose
|
||||
HTTP 502 responses through nginx. Restart the socket unit only to repair the
|
||||
socket itself, with an explicit outage window.
|
||||
|
||||
## Runtime configuration
|
||||
|
||||
Create `/etc/uce/settings.cfg` from `etc/uce/settings.cfg` and adjust paths to your checkout root. Replace checkout-specific settings such as `WASM_CORE_PATH` with `<UCE_REPO_ROOT>/bin/wasm/core.wasm` or leave it relative to `COMPILER_SYS_PATH` as appropriate.
|
||||
|
||||
Reference in New Issue
Block a user