Skip to content

feat: staging deploy infrastructure - #69

Open
dddictionary wants to merge 1 commit into
mainfrom
feat/staging-infra
Open

feat: staging deploy infrastructure#69
dddictionary wants to merge 1 commit into
mainfrom
feat/staging-infra

Conversation

@dddictionary

Copy link
Copy Markdown
Owner

Summary

  • Adds workflow_dispatch-only deploy-staging.yml that builds a :staging-<sha> image and applies k8s/staging/ manifests against the portfolio-staging namespace.
  • Mirrors prod under k8s/staging/ with its own MariaDB StatefulSet (2Gi PVC) and ingress on staging.4brar.me via nginx-internal.
  • Adds scripts/setup-staging-secrets.sh (uploads STAGING_* GH Actions secrets from a local env file) and staging.env.example documenting required values.
  • Tightens .gitignore to cover .env.* (keeps example.env + staging.env.example tracked) and client_secret*.json.

No prod paths are touched.

Test plan

  • After merge, gh workflow run deploy-staging.yml --ref feat/booking succeeds end-to-end
  • staging.4brar.me serves the site, healthcheck passes
  • kubectl -n portfolio-staging get pods shows backend + mariadb Running

- workflow_dispatch-only deploy-staging.yml builds :staging-<sha> image and applies k8s/staging manifests
- k8s/staging mirrors prod under portfolio-staging namespace with its own mariadb + ingress on staging.4brar.me
- scripts/setup-staging-secrets.sh uploads STAGING_* GH Actions secrets from a local env file
- staging.env.example documents required values
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant