4 Commits

Include renames

Author	SHA1	Message	Date
Felix KemmlerandClaude Haiku 4.5	d16a1a058e	Add SMTP email configuration via .env for password reset mail delivery ... - docker-compose.yml: Add Email__* vars for SMTP provider, host, credentials, and reset template (all referencing env vars from .env) - .env (new, gitignored): Real SMTP credentials for passwort@omsorg-pflegedienste.de - .env.example (new, tracked): Template documenting required env vars for next deploy - .gitignore: Add .env to gitignore so credentials don't leak into git history Mailversand über den bestehenden `SmtpEmailSender` (`omsorgCore/CLAUDE.md`, Abschnitt "Passwort-Reset / E-Mail-Versand") wird damit in Docker Compose aktiviert — zuvor war nur der Console-Provider (kein echter Versand) konfiguriert. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>	2026-08-10 21:46:29 +02:00
Felix KemmlerandClaude Sonnet 5	dcc8ea1510	Make omsorgapp's backend URL runtime-configurable, use dedicated API subdomain ... - omsorgapp now reads the omsorgCore URL from a runtime env-config.js generated by the container entrypoint from OMSORG_CORE_URL, instead of only baking it in at image build time - docker-compose.yml pulls pre-built images from the registry, so a build-time-only value couldn't be changed without a rebuild. - docker-compose.yml: omsorgCore gets its own subdomain (core.omsorg-pflegedienste.de) rather than being proxied under the frontend's domain - omsorgWeb never needs browser-side access to it anyway (server-side cURL only), and a dedicated API host is more future-proof without being any less secure (backend still only bound to 127.0.0.1). Includes the nginx server-block snippet needed for the new subdomain. - Drop the now-unused OMSORG_CORE_PUBLIC_URL build-arg wiring from the Gitea Actions workflow. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-10 18:14:32 +02:00
Felix KemmlerandClaude Sonnet 5	2a05c791f5	Use registry images in compose, drop MySQL/named volumes, fix omsorgWeb build ... - docker-compose.yml: pull omsorgcore/omsorgapp/omsorgweb from the Gitea registry (pinnable via OMSORG_IMAGE_TAG) instead of building locally; remove the MySQL service (mitarbeiter-app-legacy is unmaintained legacy code) and switch all persistent storage from named Docker volumes to bind mounts under /root/data/. - omsorgWeb/Dockerfile: create the upload/download/etc. directories before chown'ing them - they're excluded by .gitignore, so a fresh CI checkout doesn't have them and the build failed there (only worked locally because of leftover local test files). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-10 17:58:29 +02:00
Felix KemmlerandClaude Sonnet 5	598dfcd38a	Migrate omsorgapp to browser SPA, add Docker/CI build setup ... - omsorgapp: drop Electron, run as a plain Vite/React browser app; refresh token moves to an HttpOnly cookie (omsorgCore), CORS added for the new browser origin, document download/preview switched to Blob-based browser APIs. - Add Dockerfiles for omsorgCore, omsorgapp, and omsorgWeb, a docker-compose.yml wiring Postgres/MySQL/all three apps together, and a Gitea Actions workflow that builds and pushes images to the repo's container registry on push to main and on version tags. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-10 17:42:45 +02:00