Configurations

Basic Devproxy Config

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

The basic approach here is;

• 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

In general;

• DEVs push and pull to the dev branch

• When an RC is ready, the team lead merges the dev branch into test

  • 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

  • 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