Establish a secure, persistent hosted deployment #30
Labels
No labels
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#88 Deploy Backstage to dev and prod through Nixidy
Personal/cluster
#23 Verify the imported catalog end to end
Personal/backstage
#20 Replace Yarn with Bun before hosted deployment
Personal/backstage
#21 Establish a reproducible dependency and test baseline
Personal/backstage
#22 Add application quality gates to Woodpecker
Personal/backstage
#24 Make Forgejo discovery resilient and continuously refreshed
Personal/backstage
#32 Add SSO through the existing Keycloak instance
Personal/backstage
#62 Integrate Backstage with the shared Bun CI/CD workflows
Personal/backstage
Reference
Personal/backstage#30
Loading…
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?
Summary
Establish and verify a secure, persistent hosted Backstage deployment in the cluster's dev and prod environments. This issue is the integration gate; application work is in this repository and Kubernetes/GitOps work is in Personal/cluster.
Context
https://backstage.dev.martials.noandhttps://backstage.martials.no. An existing PostgreSQL instance runs on Nidaros, but cluster connectivity has not yet been tested.Scope
Acceptance criteria
Dependencies
Out of scope
Existing deployment precedent from the vault
Use the documented platform implementation as the starting point before asking for a new deployment design:
projects/toolbox/learnings.md: locked Bun dependencies, Nix-built OCI images, and production-startup tests exercising the same compiled artifact as deployment.projects/nixos/woodpecker-global-workflow-architecture.md: validate → publish image to Forgejo registry → open dev/prod cluster promotion PR, rather than directly deploying from application CI.projects/cluster/ci-woodpecker-pipelines.md: Nixidy/GitOps manifest generation and promotion conventions.projects/cluster/secret-management-sops.md: reference for existing secret-management conventions; verify the current implementation before adoption.Evaluate reuse of the existing Nix/OCI/GitOps path before inventing a parallel Docker-only deployment pipeline. These precedents do not yet establish that Backstage can use the Astro-oriented global workflows unchanged. Coordinate #20/#22, preserve the Bun-before-deployment dependency, and verify current configuration, persistence, identity/authorization, and private-data boundaries.