Hacker News new | ask | show | jobs
by theptip 1886 days ago
Do you have a separate git repo for the deploy config/manifests? Or just force-push your `master` branch to the `staging` and `production` branches to do a deploy (i.e. not keeping full history in the env branches)?

I've seen both advocated for, interested in what the consensus is.

1 comments

We have gitops repo which contains state of both clusters. Staging and production. The only difference is that production flux watches only production folder and production branch, while staging flux watches staging folder and master branch. Production branch is kept in sync with master when releasing, ff-only.

Backend is a monorepo. I can easily check the commit history in gitops repo to see what was the state of backend when the release was made.

Nothing should be lost, we keep history of everything this way.