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: Gagné Sébastien <>
  • To: "Mark McCoy" <>
  • Cc: <>
  • Subject: RE: [grouper-users] best practice for configuration management
  • Date: Wed, 21 Nov 2012 08:21:19 -0500

Here we have Dev/Test/Prod environment.


In SVN we reproduced the grouper folder directories for the files we modified. For files with the same configuration through every environment, we use the "standard" name, while files that are different will have tags (_dev, _test, _prod). This way we can copy the structure right on the extracted Grouper jars and then choose which file we need to remove the tag.


As for password, in the conf files we specify the path to the external password file (always the same since we use symlinks for api/ui/ws folder). When installing we create the morphString file, encrypt the password and save it in the appropriate file. That way they aren’t saved in SVN, but we could copy them through env


Here's what it looks like :


-----Message d'origine-----
De : [mailto:] De la part de Vincent Repain
Envoyé : 21 novembre 2012 05:07
À : Mark McCoy
Cc :
Objet : Re: [grouper-users] best practice for configuration management


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


> *Mark McCoy**

> *Identity Management Analyst

> The Office of Information Technology

> The University of Texas at San Antonio


> cid:


> /One place for all your technology requests/


> <>__


> <>

> 210-458-5555




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