This commit is contained in:
@@ -53,6 +53,24 @@ sudo journalctl -u ypchat -f
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
## Auto-Rollout mit Gitea
|
||||
|
||||
Der Workflow `.gitea/workflows/deploy.yml` startet bei Push auf `main` per SSH das Server-Skript `/usr/local/bin/actualize-singlechat.sh`.
|
||||
|
||||
Gitea-Konfiguration:
|
||||
|
||||
- Variables: `PROD_HOST`, `PROD_PORT`, `PROD_USER`
|
||||
- Optional: `PROD_DEPLOY_SCRIPT`, falls der Skriptpfad abweicht
|
||||
- Secret: `PROD_SSH_KEY_B64` mit dem base64-kodierten privaten Deploy-Key
|
||||
|
||||
Server-Skript installieren:
|
||||
|
||||
```bash
|
||||
sudo install -m 755 scripts/actualize-singlechat.sh /usr/local/bin/actualize-singlechat.sh
|
||||
```
|
||||
|
||||
Das Skript aktualisiert `/opt/ypchat`, baut den Client neu und startet `ypchat` per systemd neu.
|
||||
|
||||
### Service startet nicht
|
||||
|
||||
```bash
|
||||
@@ -86,4 +104,3 @@ cd /opt/ypchat
|
||||
sudo -u www-data npm run build
|
||||
sudo -u www-data cp -r client/dist docroot/
|
||||
```
|
||||
|
||||
|
||||
Reference in New Issue
Block a user