2 Commits

Include renames

Author	SHA1	Message	Date
Nick SzaunigandClaude Opus 5.5	ebeb499a18	fix(backup): keep GUI backup paths under BACKUP_ROOT and limit the schedule ... backup:configure could point automatic backups at any writable directory (e.g. a statically served one) and set a cron of every second; an invalid expression deleted the running job before failing, silently ending backups. - A path entered in the UI is resolved under BACKUP_ROOT (default ./backups) and refused if it leaves it; env values stay unrestricted. - The schedule must be a five-field cron that runs at most hourly. - reload() validates before replacing the running job. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>	2026-10-01 02:14:18 +02:00
Nick Szaunig	412d033d8d	feat: add website social link, fix herkunft origin display, GUI backup schedule, and format-based batch numbering ... - SiteSettings gains websiteUrl (e.g. online shop link) alongside the existing social links, editable in Verwaltung > Automatisierung. - /herkunft/[lot] now shows the apiary's Standort instead of its internal Name (so multiple apiaries at one location read as one origin), adds small icons per social link, and surfaces previously-fetched-but-unused data (Honigsorte, Abfülldatum, stat cards) to make the page a richer customer-facing info page. - Backup schedule (path/cron/retention) is now also configurable via the GUI (Verwaltung > Backup), stored in a new BackupSettings singleton; an env var always wins over the GUI value per field, and the scheduler reloads its cron job live when GUI settings change. - New Automatisierung rules let an admin define a format (e.g. "WH-{YYYY}-{SEQ:4}") that auto-generates HoneyBatch.batchNumber and BottlingBatch.lotNumber on creation, with an atomic per-rule sequence counter and a manual reset. Manual entry still works when the rule is inactive.	2026-09-03 13:37:09 +02:00