grouper-users - [grouper-users] best practice for configuration management
Subject: Grouper Users - Open Discussion List
List archive
- From: Mark McCoy <>
- To: "" <>
- Subject: [grouper-users] best practice for configuration management
- Date: Tue, 20 Nov 2012 20:51:35 +0000
- Accept-language: en-US
Hi all, new to the list and to Grouper…. Just wondering what everyone else is using for managing your configurations for Grouper, for example, what parts of Grouper do you put under revision control? Grouper spreads itself out under different directories and it is difficult to
know what needs to be stored in SVN or git and what isn’t needed. I’m specifically thinking about a disaster recovery scenario or a “clone the production server into a test environment ASAP to replicate a huge problem” scenario where we would do an install
using the installer and then checkout a directory or 2 (or 3) from the master repository to get a working installation up quickly. Thanks in advance, Mark Mark McCoy One place for all your technology requests
|
- [grouper-users] best practice for configuration management, Mark McCoy, 11/20/2012
- Re: [grouper-users] best practice for configuration management, Vincent Repain, 11/21/2012
- RE: [grouper-users] best practice for configuration management, Gagné Sébastien, 11/21/2012
- RE: [grouper-users] best practice for configuration management, Chris Hyzer, 11/21/2012
- Re: [grouper-users] best practice for configuration management, Vincent Repain, 11/21/2012
Archive powered by MHonArc 2.6.16.