22972 Posts in 11596 Topics by 2824 members
|Go to End|
31 May 2010 at 2:43pm
I'm wondering whether any of the experts here can provide any advice on the best way to set up a shared server to host multiple SilverStripe powered websites on a single server. We're already using named based virtual hosting, and my preference is to have a common core version of the Sapphire framework and the CMS directory, as well as other components that are commonly shared. However, hard drive space is cheap, and from what I've seen it might be easier and give us more flexibility to keep it all together and have n copies of Sapphire for each site.
The second aspect, beyond the deployment, is the management/ maintenance of sites on an ongoing basis. Through the use of the SVN:externals method, I'm wondering whether we can create our own repository for the 'mysite' content, and then tell via externals tell the SVN client when they do an update of the whole site, they should also check/update the Sapphire and CMS content from the main SVN repo.
Does anyone have any advice about this? I can see there are potentially a lot of pitfalls - particular as upgrades should be managed, with a minimum of surprises, as well as the Sapphire and CMS folders not really being "common", but instead being able to retain our own versions and configuring things as we like, only merging in changes in SS versions deliberately and occasionally - so any advice from the trenches would be much appreciated...
31 May 2010 at 5:07pm
Great question. I think there is no 'right' answer but it depends on your setup. For me personally each of my sites is very separate to each other (one might be on 2.3 and the others on 2.4, trunk) so I mantain completely separate sapphire and cms folders for each (managed via externals though). This means if I upgrade one then it won't break the other sites which is what I like. Also upgrading is a matter of changing the externals on the particular site I want to upgrade or simply running svn up to keep it up to date.
Some firms I've worked with have 1 sapphire and 1 cms folder and symlink those 2 folders into each project. This has a number of benefits namely you can update all your sites in 1 hit and saving on diskspace, downside is you can also break all your sites in 1 hit .
The SS development team strives to keep branches/2.3 and 2.4 stable for day to day usage so I just run my cms, sapphire externals directly off the svn server rather than use my own copy of it (unless you need to keep your own copy and merge individually).
1 June 2010 at 12:39am
I think is good to have one site, one install....
|Go to Top|