LibreSeal v0.1.1

Fix: nginx and the frontend now reach the backend and frontend through the unique aliases libreseal-backend / libreseal-frontend, so attaching nginx to a shared network (e.g. a PaaS proxy network) can no longer route requests to other projects' backend/frontend services. If you customised nginx/default.conf, change its two set $..._upstream lines to http://libreseal-backend:8000 and http://libreseal-frontend:3000.

What's Changed

• docs(openspec): archive publish-releases by @temperatio in #11
• fix: route nginx and the frontend through unique service aliases by @temperatio in #12
• chore(release): v0.1.1 by @temperatio in #13

Full Changelog: v0.1.0...v0.1.1

LibreSeal v0.1.0

What's Changed

• Establish LibreSeal: remove ee/ code, plans and telemetry; rebrand; reproducible self-hosting by @temperatio in #1
• Enforce network access policies (clean-room) and trust forwarded IPs only from proxies by @temperatio in #2
• ci: enable fork CI and protect main (enable-fork-ci) by @temperatio in #3
• docs(openspec): record enable-fork-ci validation by @temperatio in #5
• docs(openspec): archive enable-fork-ci by @temperatio in #6
• feat: publish signed releases (images, deployment bundle) by @temperatio in #7
• chore(release): v0.1.0-rc.1 by @temperatio in #8
• docs(openspec): record publish-releases validation by @temperatio in #9
• chore(release): v0.1.0 by @temperatio in #10

New Contributors

• @temperatio made their first contribution in #1

Full Changelog: https://github.com/Dos2Locos/libreseal/commits/v0.1.0