Repository navigation
Plan developer-only staging environment and track implementation TODO - #14
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document a TODO, not implemented developer-only staging environment. The owner confirmed scheduled availability and synthetic demo seeds. The plan preserves production business-service/contract coverage at smaller fixed capacity, with a separate small database, Redis/Kafka/media resources, secrets and Grafana Cloud observability; Cloudflare Zero Trust Access protects all staging paths and origins.
Faro stays enabled for technical errors, while Umami and every usage-analytics path stay disabled. Inspection found the existing shared telemetry flag cannot express this independently, so frontend gate/build/test work is explicitly a TODO. Compare cost-first single-node MicroK8s with dedicated EKS, identify parity/HA limitations, schedule/cost caveats, stateful recovery, resource/DB scaling restrictions, delivery boundaries and acceptance criteria. Budget, operating hours/timezone, exact hosting/sizes, domain and CDN choices remain open.
Link the plan from architecture, deployment, costs, Cloudflare, observability, frontend telemetry and delivery/backlog documentation. Track future work in issue #13. This PR changes only Markdown: no code, manifests, environment values, workflows, schedulers or infrastructure are implemented. The tracker must remain open pending separate owner authorization and acceptance evidence.
Validation: Prettier, whitespace and focused relative-link checks passed; Zensical builds without issues. All staging checkboxes remain unchecked. Root pre-commit was attempted but no root hook configuration exists. Existing CI checks run on the PR. Owner's existing authorization covers documentation review/merge, not staging deployment.