# Configurations

## Basic Devproxy Config

<img src="/files/cPfu0BI65U1yBr5C4dN2" 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;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://engine.sygnal.com/devproxy/configurations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.