admin/omsorg
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

0 Releases 7 Tags

RSS Feed
  • v0.1.2 dcc8ea1510
    Compare

    Make omsorgapp's backend URL runtime-configurable, use dedicated API subdomain
    Docker-Images bauen und veröffentlichen / build (, omsorgCore/Dockerfile, omsorgcore) (push) Successful in 3s
    Details
    Docker-Images bauen und veröffentlichen / build (, omsorgWeb/Dockerfile, omsorgweb) (push) Successful in 3s
    Details
    Docker-Images bauen und veröffentlichen / build (, omsorgapp/Dockerfile, omsorgapp) (push) Successful in 3s
    Details

    admin released this 2026-08-10 16:14:32 +00:00 | 8 commits to main since this release

    • 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

    Downloads