Skip to content

Deploy and verify the unified business site and private portal #3939

Open
14 of 16 issues completed
Open

Description

@devantler

🤖 Generated by the Agentic Engineer

User Story

As the sole operator, I want the portal to run reliably within a bounded cost on the existing platform, so that handling small client projects does not create an oversized support burden.

Acceptance Criteria

  • Deploy one unified business-site application from devantler-tech/business-site: built public pages plus the private /portal server and its restricted store, with an immutable combined artifact/source receipt. Follow the reviewed platform tenant/secret/certificate/network contracts and keep customer access separate from infrastructure/operator access. Do not create a separate client-portal product, repository or competing publisher.
  • Use the current platform's KRO Tenant/WebApp abstraction and reviewed schema, not a copied legacy namespace/RBAC/Flux skeleton. Preserve namespaced tenant access, signed OCI verification and the default-deny network floor; the platform's accepted tenant decision takes precedence over generic onboarding examples.
  • Publish reviewed signed immutable combined application artifacts; the portal remains closed/default-off until release checks pass while public pages remain usable. Keep the current Pages publication until the replacement runtime is verified. Document protected same-site cutover and rollback without simultaneous competing publication. Do not expose a demo login or fixture identity on the public service.
  • Use durable storage with migration concurrency protection, bounded connection/resource settings and tested backup/restore, including retained order/contact history after restart.
  • Provide readiness/liveness checks, privacy-safe operational logs, failure visibility, a rollback/recovery procedure and a documented operating footprint against the maintainer's approved budget.
  • Static validation, affected tests and staging/live readback observe the actual enacting deployment path; no cluster mutation from the agent shell or unapproved paid service.
  • Real provider sign-in, two-customer isolation, the sequential operator path and existing EN/DA Home/Projects/Journal paths pass at the combined deployed revision before cutover/public activation. Test private route handling, static fallback, cache isolation, cookies, redirects, locale/appearance and portal-off public-site continuity. Name missing prerequisites rather than marking an untested surface ready.

Size: M. Depends on the implementation decision and application slices. Deployment design is not evidence of live adoption; retain sanitized receipt of the actual running revision.

Activity

  1. added theissue type on Oct 7, 2026
  2. changed the title [-]Deploy and verify the client portal within its operating budget[/-] [+]Deploy and verify the unified business site and private portal[/+] on Oct 9, 2026
  3. devantler commented on Oct 13, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Next visible business delivery — 13 October 2026

    Fresh native child reads show combined runtime #44 and signed distribution #46 CLOSED, and identity/browser/contact source children #33/#40/#49 CLOSED. These completed source foundations must not be presented as a customer-usable portal. Proposal #64 remains draft delivery PR #66 at bfa39b94cc56a89145c6ef8e4c88ed9215543283; no merge or activation is inherited from that work.

    The next visible outcome should finish this existing deployment programme together with #3936: an invited synthetic client opens the staged HTTPS site, signs in through its privately configured federated broker, accesses only its own contact profile, and signs out; public EN/DA Home, Projects and Journal remain usable. Do not add another queue/executor before that path is demonstrated.

    One concrete source prerequisite remains: the actual executable installs the OpenFeature no-op provider. server/README.md explicitly states that no production activation provider is wired. Broker/database settings alone cannot open identity. Select and implement a reviewed operator-controlled activation path in business-site, preserving false/error/unset refusal and independent operation-time gates; configuration or deployment must never silently enable requests, proposal dispatch, agreements, payments or worker/API/MCP powers.

    Keep the existing finite launch conditions, not a replacement parent:

    1. Prove the current KRO Tenant/WebApp and private secret/network/TLS contracts, immutable signed source/digest, restricted migrated store, measured resource/cost bounds, restart/backup/restore, rollback and privacy-safe operational visibility through the reviewed enacting path. No direct agent-shell cluster mutation or paid enrollment.
    2. Complete broker/provider registrations privately, then prove actual deployed login/logout, revocation and two-client/operator isolation. Existing synthetic broker fixtures do not establish Google/Microsoft registration or live federation.
    3. Complete the processing/recipient/retention notice before real contact collection under business-site#19 and the applicable privacy portion of Bump projects/ksail from c59cd63 to c5fcbb2 #21. Reported iCloud Cleanup remains insufficient proof of enquiry retention; do not invent a policy or repeat the existing pending question.
    4. Preserve the separate invited-consumer/business contract, tax, durable confirmation and withdrawal/cancellation conditions of Bump projects/ksail from c59cd63 to c5fcbb2 #21 before binding transactions. Proposal preparation is not acceptance or credited funds.

    Retain own-repository Pages until the replacement runtime and protected same-site cutover/rollback are verified. One unified source/publisher remains the product boundary; no client-orders repository, parallel portal product or competing production publisher is introduced. These are verified scope/prerequisite observations, not current deployment health, provider availability, legal approval or a launch date.

  4. devantler commented on Oct 13, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Merged staging prerequisite — 13 October 2026

    Business-site #69 is CLOSED and its board item is Done. PR #70 was normally protected squash-merged at 3ab5d91ffd878d2193ae5655edeaddbeeb42ec8c after a clean exact-head Codex review and settled promotion CI. The actual executable now has the maintained, bounded operator-only identity provider instead of an exclusively no-op composition. False/error/stale/expired/cancelled/shutdown states deny, and requests, proposals, funds and worker/API/MCP powers remain independently closed.

    Merged-source CI 38394574836 and own-repository public publication 38394574820 succeeded. The live receipt names the final business-site source; actual post-publication EN/DA Home, Danish Projects, Journal and native article navigation pass. Both main runtime archives were read back and their digests recomputed. The production-template image digest 365af25872f35f5d05154845713bea830499e3983ab99db70bddf1e345933051 has locally verified source-owned signature/provenance, and the main pipeline pulled and exercised that exact digest. Full evidence: devantler-tech/business-site#70 (comment).

    Fresh child reads also confirm #33/#40/#49, #44/#46 and #67 CLOSED. Proposal child #64 and PR #66 are now CLOSED/MERGED at 84d32e24898122a4b165dfa057f710ae048d7dfc; the earlier draft observation is historical. These are source outcomes, not activated customer operations.

    Keep this programme and #3936 OPEN. The next visible outcome remains the reviewed staged HTTPS runtime and configured-broker login/logout with two isolated synthetic clients, preserved public paths, restricted storage, recovery and measured operating bounds. Real-provider/deployed proof, privacy #19 and applicable legal #21 conditions are still outstanding. Keep existing source-owned Pages until protected cutover/rollback is proved; no separate portal product, client-orders repository, new queue/executor, real customer collection, payments or paid enrollment was introduced here.

  5. 13 remaining items

  6. devantler commented on Oct 18, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Hosting direction from the maintainer's Pages review — 18 October 2026

    The maintainer directs us to stop the AS Coaching migration to Pages and vet other portfolio Pages uses. AS Coaching #206 is now closed NOT_PLANNED; it had not migrated. The new policy spike records the current portfolio census and follow-ups.

    For the Devantler Tech business site, use this existing application-hosting work as the replacement path rather than creating another publisher or relying on Pages for commercial business operation. Public source can remain public; source visibility, static rendering and hosting eligibility are different decisions. GitHub's Pages terms require purpose-specific review; this is a conservative hosting decision, not a claim of a GitHub enforcement finding.

    Refine a bounded public-site-only cutover if the unified application's portal prerequisites would otherwise unnecessarily hold it: the already-tested public artifact can be served while private identity, intake and payments remain closed. Keep one source-owned application/publisher, the existing platform ownership, current source/digest verification, client isolation and cost approval. Do not loosen a platform gate or enable an unverified private route to accelerate the move.

    Before any production change, prove replacement EN/DA Home/Projects/Journal and legacy paths, permitted company-disclosure handling, DNS/certificate ownership, source receipt, health/recovery and rollback. Retire Pages only after the replacement is verified. This planning update does not unpublish the current site, dispatch a deploy, contact a provider, authorize new spend or claim portal activation. Keep the wider unified-runtime acceptance criteria intact.

  7. devantler commented on Nov 13, 2026

    @devantler
    ContributorAuthor

    Portal address — 13 November 2026

    The maintainer set where the portal lives: "The business site portal should be available on portal.devantler.tech or devantler.tech/portal". It will be portal.devantler.tech. The public site stays on GitHub Pages at devantler.tech, and the portal gets its own origin on the platform.

    The devantler.tech cutover is no longer a portal gate. Don't move the public site off Pages to launch the portal. Moving the public site off Pages stays open as its own later step under the 2026-10-18 Pages-hosting direction above; the maintainer confirmed it is still planned.

    Work:

    The remaining portal gates are unchanged: self-hosted ZITADEL sign-in, which waits on the business mail sender (business-site#302, then devantler-tech/platform#5400); the Danish-law checklist (business-site#19); switching sign-in on; and the Numina and Stripe billing work (business-site ADR 0030, business-site#551).

    🤖 Generated with Claude Code

  8. devantler commented on Nov 13, 2026

    @devantler
    ContributorAuthor

    Public site move — priority, 13 November 2026

    The maintainer made moving devantler.tech off GitHub Pages a priority alongside the portal: "I am pretty sure we cannot keep running the devantler.tech site in github pages as it is commercial. I do like portal.devantler.tech the most, but moving devantler.tech to the platform is also a priority".

    This replaces "later, separately" in the portal-address comment above. The move is part of this programme, right after the portal host, and the agents carry it through.

    End state: one business-site app serves devantler.tech (the public pages) and portal.devantler.tech (the portal). Each host redirects the other's paths, so nothing appears twice.

    Order:

    1. feat(business-site): reconcile the public staging app behind its hold platform#6174 (tenant up under the staging name) and its hold removal.
    2. One business-site release with per-host routing and both routes (business-site#555, reworked).
    3. A platform PR for listeners, certificates, the route allow-list and the Tenant re-pin (Serve devantler.tech and portal.devantler.tech from the platform platform#6177). The portal host comes up first.
    4. The devantler.tech cutover: verify the platform serves every public path, hand the apex and www records to the platform's external-dns, verify live, then retire the Pages publication. Rollback is restoring the Pages records until the switch is verified.

    🤖 Generated with Claude Code

  9. devantler commented on Nov 15, 2026

    @devantler
    ContributorAuthor

    Public site moved off GitHub Pages (15 November 2026)

    Step 4 of the order above is done. devantler.tech and www.devantler.tech are served by the business-site app on the platform. GitHub Pages is unpublished and its workflow removed. Parity was proven on all 305 public paths before the switch, and the switch was verified live after it. Details: devantler-tech/platform#6177.

    • Pages publication is retired (business-site#586), so there is one publisher.
    • The portal stays off: portal.devantler.tech/portal/ answers 404.
    • The remaining portal gates in this programme are unchanged.

    🤖 Generated with Claude Code

  10. devantler commented on Nov 16, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Portal database backup and restore: proven (first run). devantler-tech/platform#6391 adds Verify Portal DB Restore, modelled on the Wedding restore proof. Its first production run, 43797796595 at f3016c0, succeeded:

    • Backup taken: a fresh backup of business-site-portal-db through its Barman Cloud ObjectStore. The proof waited until the WAL segment holding the live snapshot was archived.
    • Restore completed: that exact backup was restored into a run-owned temporary namespace with a one-instance cluster and no WAL archiver.
    • Isolation proven: a Cilium deny rule stopped the restored pod reaching the production database. As a positive control, a live instance did reach it.
    • Aggregates matched: only counts and ownership were compared: the database owner (portal_migrator), the schema ledger and the table set.
    • Cleanup verified: the temporary namespace and its volumes are gone, and business-site-portal-db is healthy (2/2).

    Limit: the portal migration Job hasn't run yet, so this run compared an empty schema (ledgerEmpty: true). I'll run the proof again after the first migration, so the real schema and row counts are covered before inviting real customers is called safe.

  11. devantler commented on Nov 16, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Portal database backup and restore: proven on the migrated schema. The first portal migration ran at 03:38 UTC (portal schema migration completed, v3.10.0). I then ran Verify Portal DB Restore again: 43799534720 succeeded.

    The receipts: backupTaken, restoreCompleted, isolationProven, aggregatesMatched and cleanupVerified are all true, with ledgerEmpty: false and highestVersion: 25. A fresh backup restored in isolation, with the migration ledger, the owner and every managed table's row count matching production, then was cleaned up. This closes the earlier run's empty-ledger limit.

  12. devantler commented on Nov 16, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Portal sign-in is switched on, invite-only, and verified live (2026-11-16).

    Gates before inviting real customers

    Known, not blocking

    • Creating an invitation needs kubectl exec into a web pod, and the everyday OIDC login is read-only. So each invitation currently needs break-glass admin access.
    • A signed-out visitor to the portal root sees "Sign-in could not be completed…". This is deliberate, so a signed-out visitor and a non-member get the same response, but the wording is misleading on a first visit.
  13. devantler commented on Nov 16, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Sign-in no longer needs an invitation code (business-site v3.12.0, devantler-tech/platform#6406), verified live on 2026-11-16.

    • The sign-in page has no code field, just Sign in. It still hands off through login.devantler.tech to ZITADEL's Customers page.
    • An invitation now belongs to the ZITADEL user it was made for, and that user's first sign-in accepts it. Any other identity is refused. The invite command prints no secret.
    • Only one invitation can be pending per identity, and redeeming one is atomic. An expired invitation and no invitation show the same refusal.

    The maintainer's two test sign-ins can go ahead now. The remaining gates are unchanged: test sign-in and sign-out, two-customer isolation, then the agent confirms it's safe to invite real customers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    Priority

    None yet

    Start date

    None yet

    Target date

    None yet

    Effort

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions