chore: sync staging environment setup to main#202
Merged
zainfathoni merged 4 commits intomainfrom Jan 10, 2026
Merged
Conversation
Add Kamal configuration and GitHub Actions workflow for deploying to staging.kelas.rumahberbagi.com. Staging deploys trigger after CI passes on the staging branch, using environment-scoped secrets.
- Add sync-staging-db.sh to copy production data to staging - Add backup-staging-db.sh with 7-day retention - Add download-staging-backup.sh for local backup retrieval - Add StagingBanner component shown when STAGING_ENVIRONMENT=true - Update deployment.md with staging environment section
feat: set up staging environment
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.
Summary
Sync staging environment configuration files to main branch so GitHub Actions can recognize the Deploy Staging workflow.
The
workflow_runtrigger requires workflow files to exist on the default branch (main).Changes
Test plan