Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] best practice for configuration management

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] best practice for configuration management

Chronological Thread 
  • From: Vincent Repain <>
  • To: Mark McCoy <>
  • Cc: "" <>
  • Subject: Re: [grouper-users] best practice for configuration management
  • Date: Wed, 21 Nov 2012 11:07:16 +0100

Le 20/11/2012 21:51, Mark McCoy a écrit :

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 McCoy**
*Identity Management Analyst
The Office of Information Technology
The University of Texas at San Antonio


/One place for all your technology requests/ <>__


Here's what i keep in a repository to be able to deploy Grouper quickly from apiBinary, ui and psp tar.gz (didn't try grouper Installer yet) :

grouper.apiBinary :
/conf/* (including psp config)
/bin/ (jvm options)

grouper.ui :

For Jasig CAS authentication ( :

So, even if there seems to be a lot of directories, customization files are quite limited.

Vincent Repain
INSA de Rennes
Centre de ressources informatiques

Archive powered by MHonArc 2.6.16.

Top of Page