We have a 6.1 site that is load balanced, it has 2 nodes and it's configured to share everything using a SAN for the media and examine indexes.
We do a source control push to upload files and usync to copy any document types from test to live.
For content editing everything works fine, but, I want to install contour and need to install future modules, from my understanding i'll have a file deployment issue.
If I install a module from live , files will be installed in the bin, plugins folder etc... outside of source control on one node but they won't be on the other nodes, the only way around this is to share the whole site on the san?
Is this the correct approach as it seems a bit wrong, how do people deal with modules and source control?
By modules, do you mean packages? I'm going to assume so.
I think the answer is that few people have sufficient reason to load balance a website, but don't have the concern about what a package might do to your website (e.g. break it). I would always suggest that you install a package locally or at least on a dev server first and then load it to live.
However for the sake of argument, I'd suggest that as it is a manual process installing a package then you could bring down server 1, install the package on this, and if all is good then you can turn it back on and bring down server 2, and install the package on server 2. That should work fine. The final alternative would be to have all your files (bin folder and all) on your SAN. That might slow down your site however.
Umbraco Load Balancing Help
We have a 6.1 site that is load balanced, it has 2 nodes and it's configured to share everything using a SAN for the media and examine indexes.
We do a source control push to upload files and usync to copy any document types from test to live.
For content editing everything works fine, but, I want to install contour and need to install future modules, from my understanding i'll have a file deployment issue.
If I install a module from live , files will be installed in the bin, plugins folder etc... outside of source control on one node but they won't be on the other nodes, the only way around this is to share the whole site on the san?
Is this the correct approach as it seems a bit wrong, how do people deal with modules and source control?
By modules, do you mean packages? I'm going to assume so.
I think the answer is that few people have sufficient reason to load balance a website, but don't have the concern about what a package might do to your website (e.g. break it). I would always suggest that you install a package locally or at least on a dev server first and then load it to live.
However for the sake of argument, I'd suggest that as it is a manual process installing a package then you could bring down server 1, install the package on this, and if all is good then you can turn it back on and bring down server 2, and install the package on server 2. That should work fine. The final alternative would be to have all your files (bin folder and all) on your SAN. That might slow down your site however.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.