This functionality is supposed to allow you to select which containers within your container group can be automatically replicated based on load. An example of where this functionality would be useful:
You create two containers, one nginx (which can handle 20,000 connections a second) and a second container php-fpm which is configured to handle 1000 requests a second. In the Tredlyfile for the php-fpm container you set replicate=yes. When you publish your containers, only one instance of each container is published BUT when the load on the php-fpm container gets high, Tredly-Host detects this and replicates the php-fpm container so now the nginx container has two php-fpm containers it can use.
If you wish to implement this functionality, please feel free to do so. If not, this functionality is tabled to be implemented after a few other improvements to Tredly. We will keep you posted.
laurieodgers
commented
8 years ago
This functionality is supposed to allow you to select which containers within your container group can be automatically replicated based on load. An example of where this functionality would be useful:
You create two containers, one nginx (which can handle 20,000 connections a second) and a second container php-fpm which is configured to handle 1000 requests a second. In the Tredlyfile for the php-fpm container you set replicate=yes. When you publish your containers, only one instance of each container is published BUT when the load on the php-fpm container gets high, Tredly-Host detects this and replicates the php-fpm container so now the nginx container has two php-fpm containers it can use.
If you wish to implement this functionality, please feel free to do so. If not, this functionality is tabled to be implemented after a few other improvements to Tredly. We will keep you posted.