Garaj

LaFix infrastructure & deployment reference

Everything the team needs in one place: where each environment lives, and how code travels from a branch on your machine to a client demo.

Environments

Bookmark these. Dev updates on every merge to develop; staging only when the team decides to promote.

Deployment workflow

Nobody commits straight to develop or main. Every change goes through a branch and a pull request.

Work on a new branch

Branch off develop for anything you touch โ€” feature, fix, or experiment. One branch per piece of work, so it can be reviewed and reverted on its own.

Open a PR into develop

When the work is finished, open a pull request on GitHub targeting develop. Get it reviewed, then merge. Direct pushes bypass review and CI โ€” don't.

Merging deploys to dev automaticallyautomatic

The merge into develop triggers the pipeline, which ships to the development environment. No manual step on your side.

After the pipeline goes green, give CapRover 1โ€“2 minutes to build the images and swap the old site out. If your change still isn't live after 2 minutes, contact Dorin directly โ€” the deployment didn't pull through.

The team decides to promote

Once everything on dev is validated and we agree as a team that it's ready to move, we promote it as a batch โ€” not piece by piece.

Open a PR into mainstaging

Promoting means a pull request from develop into main. Merging it deploys to the staging environment โ€” same 1โ€“2 minute CapRover build window.

Staging is what we put in front of clients for demos, and the environment we harden on the way to production.

Quick reference

Which branch lands where.

Branch Merged via Environment Used for
your-branch โ€” local only Your work in progress
develop PR from your branch Development Integration & day-to-day testing
main PR from develop Staging Client demos & pre-production

Rules of thumb