Upgrade Guide
An update is straightforward, since schema changes run automatically on the first request after the update:
- Before updating: create a backup (Settings → Backup & Export, or back up
/backupsfor Docker). - Apache: copy the new files over the old ones, or
git pull— just don’t overwrite or deleteconfig.php,paragrafy_data.sqlite, and/backups. Docker: firstgit pullin the local checkout, thendocker compose up -d --build— the image is built from the local code, so a plain--buildwithout a precedinggit pullstill uses the old state.config.php,paragrafy_data.sqlite,/backups, and.env.localare preserved automatically via thedatavolume. - On the next request to any page,
ensure_schema_migrations()automatically creates missing tables and columns (e.g.users,audit_log,translation_versions,webhook_queue, new columns inprojects) — no manual migration script needed. - Existing installations without a
cron_secretinconfig.phpget one generated automatically on the first request to an/api/cron/...endpoint (visible under Settings → Automation).
There have been no breaking changes so far requiring manual intervention beyond the automatic migration.