# Configurations

## Basic Devproxy Config

<img src="https://3849716756-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbZeVxnZi0ThYsR4w1hXd%2Fuploads%2F1Pmrhj3FScJMWfxNT19g%2Ffile.excalidraw.svg?alt=media&#x26;token=3c2906e5-a68e-4d94-9b51-3a96c80be88f" alt="" class="gitbook-drawing">

## More Advanced Devproxy Config

For large teams on large projects with heavy CI/CD requirements, it's possible to separate the TEST environment.  This is most useful when;

* You have multiple devs working concurrently
* The TEST platform needs to be a vetted "release candidate" stage of content&#x20;

The basic approach here is;&#x20;

* Add a `test` branch to your Github repo
* Point the TEST code host in Netlify to the `test` branch ( instead of `dev` )
* Formalize the promotion of the `dev` to `test` branch merges&#x20;

In general;

* DEVs push and pull to the `dev` branch
* When an RC is ready, the team lead merges the `dev` branch into `test`&#x20;
  * This `test` commit automatically gets picked up by Netlify, and published to the TEST code server
* Testing team evaluates it using `test.mysite.com`
* When a release is confirmed, the release manager merges the `test` branch into `main`&#x20;
  * This `main` commit automatically gets picked up by Netlify, and published to the PROD code server
  * At the same time, any changes in Webflow would also be published so that the new HTML/CSS design changes are synchronized with the PROD code release&#x20;