We use a trunk-based deployment model. Merging toDocumentation Index
Fetch the complete documentation index at: https://docs.yupvid.com/llms.txt
Use this file to discover all available pages before exploring further.
main triggers a staging deploy automatically; production deploys are triggered manually after verification.
Flow overview
Deploying to staging
Every merge tomain triggers a staging deployment automatically via CI. You don’t need to do anything. Check the #deploys Slack channel for status notifications.
Staging deployments take approximately 5–10 minutes. If a deploy fails, CI will post the error in #deploys with a link to the failed run.
Promoting to production
Once a change is verified in staging:- Go to the deploy tool (link in
#deployschannel description). - Select the staging build you want to promote.
- Click Promote to production.
- Monitor the
#deployschannel for confirmation or errors.
Feature flags
Most new features are deployed behind a feature flag to decouple deploy from release. Flags are managed in [Flag Tool Name]. Ask your tech lead about the flag naming convention and cleanup process.Rollbacks
If a production deploy causes an incident:- Use the deploy tool to roll back to the previous production build immediately.
- Don’t wait to diagnose — roll back first, investigate after.
- File an incident and start a postmortem if users were affected.
Database migrations
Migrations run automatically as part of the deploy pipeline. Backward-incompatible migrations require a multi-phase deploy — ask in#eng before merging if your migration drops a column or changes a type.
Deploy freeze windows
We freeze production deploys during major events or the last business day before a holiday. The#deploys channel will pin a message when a freeze is active.