2 Commits

Include renames

Author	SHA1	Message	Date
maroandClaude Sonnet 5	8d60d48bd0	Fix .env writer: quote values so shell metacharacters don't break source ... deploy.sh sources .env directly as bash (`set -a; source .env`), but setup.sh wrote raw unquoted values. The default SMTP_FROM ("ANOUMA <no-reply@...>") contains `<`/`>`, which bash parses as redirections, failing with "syntax error near unexpected token `newline'" on every deploy. Both scripts' env_set now write double-quoted values with backslashes/quotes escaped — valid for both `source` and Docker Compose's env_file parsing (which strips matching quotes). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-26 02:12:24 +02:00
maroandClaude Sonnet 5	56b2a6497b	Overhaul deployment to Gitea Actions CI/CD, remove update.sh ... Production no longer builds from source or self-updates via cron/git pull: setup.sh now only provisions the server once (Docker, /opt/anouma, a restricted `anouma-deploy` SSH user whose key can only ever run deploy.sh, generated secrets). All future deployments run through .gitea/workflows/ci.yml (lint/typecheck/test/build on every push) and release.yml (on a vX.Y.Z tag: build the image, push it to the Gitea registry, then SSH-trigger deploy.sh on the server), which pulls, migrates, restarts, healthchecks, backs up the database first, and automatically rolls back the code on a failed healthcheck. docker-compose.yml's app service now runs a registry image (${ANOUMA_IMAGE}) instead of building locally. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-25 22:58:09 +02:00