Add polling Docker deployments
Co-authored-by: Heaust Azure <heaust.azure@gmail.com>
This commit is contained in:
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user