Add polling Docker deployments

Co-authored-by: Heaust Azure <heaust.azure@gmail.com>
This commit is contained in:
Amp
2026-08-22 07:09:49 +00:00
co-authored by heaust
parent eb7508d1c1
commit df8b69e09d
3 changed files with 96 additions and 6 deletions
+10
View File
@@ -41,6 +41,16 @@ prebuilt package assets, Monaco, and the persistent SQLite volume. Configure the
path in `compose.yaml`. The default port binding is private to the VPS at `127.0.0.1:5002`; put
Caddy or nginx in front of it for HTTPS. Follow logs with `docker compose logs -f yawn`.
To check for new pushes every minute, add this entry with `crontab -e`:
```cron
* * * * * $HOME/yawn/server/poll-deploy.sh >> $HOME/yawn-deploy.log 2>&1
```
The poller compares `origin/main` with the last healthy deployed revision and does nothing when they
match. A shared lock prevents overlapping manual and scheduled deployments. Failed deployments do
not update the revision marker, so the next poll retries them.
Run the previous VitePress documentation site with `npm start`.
Run `npm run coredocs` for the raw worker-message, shared-memory, and render-graph reference intended for custom handles, editors, and direct SAB clients.