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 repoPoint the TEST code host in Netlify to the
test
branch ( instead ofdev
)Formalize the promotion of the
dev
totest
branch merges
In general;
DEVs push and pull to the
dev
branchWhen an RC is ready, the team lead merges the
dev
branch intotest
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 intomain
This
main
commit automatically gets picked up by Netlify, and published to the PROD code serverAt 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
Last updated