Keeping cluster updated
Using Jamroom
As I build out my cluster, I am now starting to think about how to keep it updated; especially during beta when updates are frequent.
I realize for a single server setup, Jamroom's marketplace works pretty well. It can see which modules are installed and licenses, you get notifications if there is an update, and you simply log in and do and update (pull) from the marketplace via the ACP.
When working with multiple servers, this was not ideal. I was running dev, qa, and prod environments. Since I was using git (actually bitbucket) to manage different branches, I set up webhooks to a script on each server that pulled from the appropriate branch (dev-->dev, qa-->qa, prod-->prod). This works great during development, however it presents a problem for making jr core updates. If I use the marketplace update, my the server gets updated and I have to manually log into each server and commit the code and push it to the repo. The better solution is to manually push the code to the repo, and then all the servers can be updated automatically.
Now with the deployment of the new cloud servers, there is a new challenge: not all the servers get the same modules. i.e., there are many modules on the main jamroom app server that don't get deployed to all servers. This makes it even more difficult to update multiple servers.
I am looking for possible solutions for PUSHING updates to the jamroom servers. However, each server must receive a different set of modules.
Any ideas?
Also, Is there any way to set up you own marketplace so you can have the server update your custom skins and modules as well?
updated by @dannya: 03/22/15 07:44:54PM
