On Tue, Sep 18, 2012 at 1:25 PM, Benjamin Ryan <benjamin.r...@manchester.ac.uk> wrote: > Don't think I made myself clear, each server will have its own > dspace.cfg setup for the initial deployment and then the rsync should just > copy over what has changed in the core API and modules but not the config etc. > This will work will it not?
OK, I misunderstood. But the 3.0 approach is also suitable for staging/production environments, just a bit different strategy. It should work fine, as long as you remember to keep the config directory and code in sync. You'll have to pay attention during upgrades to a new upstream major version, because there are sometimes incompatible changes (although we strive to minimize them). E.g. accidentally using my old config from 1.8 with code from the current master branch bit me in the butt just last week. But of course you know that already, I just thought it's worth pointing out. Regards, ~~helix84 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
