- 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>
Consolidates the previously separate omsorgapp and omsorgCore repos
(each had their own nested .git with GitHub history) plus the old
root-level website/mitarbeiter-app into a single monorepo, matching
the structure already documented in the root CLAUDE.md. Also moves
the PHP employee app aside as omsorgWeb/mitarbeiter-app-legacy/ to
serve as a template for a ground-up rewrite.
Fixes .gitignore in the same pass: the config-secrets/uploads/data
patterns were unanchored (relative to repo root, not depth-agnostic),
so they silently stopped matching once the app moved under omsorgWeb/.
Patterns are now **/-prefixed and cover both mitarbeiter-app and
mitarbeiter-app-legacy, keeping DB/SMTP credentials and uploaded
employee documents out of version control.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>