History

pavlov346346-source 1cc1220e20 Ops: document Timeweb panel cron deploy		2026-09-10 18:51:00 +03:00
..
caterium-production-sync.sh	Ops: add safe Timeweb production sync	2026-09-10 18:50:50 +03:00
README.md	Ops: document Timeweb panel cron deploy	2026-09-10 18:51:00 +03:00

README.md

Timeweb fallback auto-deploy

Use this only for the Year/shared-hosting fallback where system crontab is unavailable and scheduling is configured in the Timeweb panel.

What it does

caterium-production-sync.sh checks the GitHub production branch, deploys only when the commit changed, validates that public/index.html exists, creates a rollback archive before changing live files, prevents overlapping runs, and keeps the four newest backups.

Timeweb panel Crontab

Create one task that runs every 5 minutes.

Command:

/bin/sh "$HOME/caterium-production-sync.sh" >> "$HOME/.caterium-deploy/cron.log" 2>&1

Copy ops/timeweb/caterium-production-sync.sh from this repository to:

$HOME/caterium-production-sync.sh

If the live document root is not auto-detected, prefix the command with the exact path, for example:

CATERIUM_WEB_ROOT="$HOME/caterium.ru/public_html" /bin/sh "$HOME/caterium-production-sync.sh" >> "$HOME/.caterium-deploy/cron.log" 2>&1

The deploy checkout uses the already configured GitHub SSH access. The old Cloudflare Worker must remain enabled as a fallback until the Timeweb production domain, SSL, Supabase flows, uploads and PDF generation have been verified.