In light of some recent issues I was thinking of a couple of things that I would like to do and wanted to see if it's something you guys could provide some guidance on.
1. It would be great if we could have a script we could execute from acp that would allow us to back up the entire configuration of all the modules. There would also be a restore button so that if we did a fresh install, the previous configuration of all the modules would instantly be loaded.
2. When deploying a new server, I would like to have configuration file that configured all the modules. Ideally, you would just change the variable settings ,such as server name, in the config file. This would allow for fast deployment of servers for scalability purposes. For example, if i wanted to create an AWS autoscale group of conversion servers, I could create an AMI with the lamp stack, the jr files, and a config file with variable server names for each instance. (yes I would still have to register each instance with the queue server).
This is how all major media platforms manage their variable scaling needs. However currently, configuring a server to just handle conversions is too time consuming to do manually. We need to be able to do dynamically with a config file. I'm sure it could be done today, but not sure how.
updated by @dannya: 02/15/16 12:57:11AM
JAMROOM
