Hi Joy, Yes this is possible. An allura system has 4 main services:
* mongo database * solr * allura taskd (background job service) * allura webapp You can run those on separate machines, and you can run multiple instances of taskd and the webapp if you want to scale out and have redundancy. Mongo and solr need to have one master server, but can be configured with secondary slaves ready for failover. We run a configuration like that at SourceForge and it works well. If you're going to run git, mercurial or subversion services, those also can be on separate machines, with a shared directory so that Allura can display the repositories. Let us know if you have any other questions, I know the docs don't cover everything, but we'll be glad to help here. -Dave On 7/17/14 5:24 PM, Joy P. Ku wrote: > We are considering migrating our current software forge to Allura but > would very much like to set up the new site with components distributed to > different virtual machines. In our current site, we run everything off of > one server but find that approach is limiting in terms of flexibility for > maintaining the site (e.g., being able to just take one component like the > wiki off line for updates). It also means that if one part breaks, the > whole site goes down. So we'd very much like to migrate to a set-up where > the internal components could be set up on virtual machines. Is it > possible to get this to work for Allura and maintain performance? Have > others done this before, and if so, what have their experiences been? > > > > Thanks for any input you can provide! > > Joy > > > > --- > > Joy P. Ku, PhD > > Director, <http://simbios.stanford.edu/> Simbios > > Director of Communications & Training, <http://opensim.stanford.edu/> > NCSRR > > Stanford University > > > > (w) 650.736.8434, (f) 650.723.7461 > > Email: <mailto:[email protected]> [email protected] > > > > -- Dave Brondsema : [email protected] http://www.brondsema.net : personal http://www.splike.com : programming <><
