External exposure: files.c0rdyceps.ch + rename cairn-enc → cairn #22
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Cordy/Cairn#22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Expose the canonical instance for real (remote) dogfooding by Nikola + Manuel.
files.c0rdyceps.ch→ the k3s instance (Basic-auth-over-plain-HTTP must stay LAN-only until TLS is in front).cairn-enc(.249) → plaincairn; add the external redirect URI to the Keycloakcairnclient; updateredirectUrlin config.Was parked "until real competitor"; pulled into v0.4 since real-world dogfooding needs remote access.
Closing as out-of-scope for the product. Clarified 2026-07-29: Cairn is sold as a self-hosted license — customers run their own instances; we never host Cairn for them. So
files.c0rdyceps.chand thecairn-enc → cairnrename are purely personal dogfood infrastructure (remote access to Nikola/Manuel's own instance), not product or launch work — nothing about a public launch depends on them.Reclassified as homelab-backlog convenience; can be done anytime at leisure, entirely separate from the Cairn roadmap. The business infrastructure that does stay ours to run (license.swisscairn.ch, www.swisscairn.ch) is unaffected.