Setup of the Divio CMS Repositories
All Divio projects (django CMS, Python, PHP, whatever) have a Live and Test environment.
By default, both build the project from its repository's master branch (in older projects, develop). 
On request, custom tracking branches can be enabled, so that the Live and Test environments will build from separate branches.
When a build successfully completes, the Docker image can be reused until changes are made to the project's repository. This means that after a successful deployment on Test, the Docker image doesn't need to be rebuilt, and the Live environment can be deployed much faster from the pre-built image. (Obviously this is only possible when they are on the same branch.)
The Divio Django CMS offers two servers: TEST and LIVE. Are these also two separate repositories? Or how is this done in the background?
I'm wondering because I would have the feeling the LIVE server is its own repository that just pulls from the TEST whenever I press deploy. Is that correct?