Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] Grouper design call, Wednesday, 19 September 2007, 1200EDT (1600Z)

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] Grouper design call, Wednesday, 19 September 2007, 1200EDT (1600Z)

Chronological Thread 
  • From: "GW Brown, Information Systems and Computing" <>
  • To: Jessica Bibbee <>, Grouper Dev <>
  • Subject: Re: [grouper-dev] Grouper design call, Wednesday, 19 September 2007, 1200EDT (1600Z)
  • Date: Wed, 19 Sep 2007 16:09:19 +0100

Apologies for the late posting.

--On 18 September 2007 13:21 -0400 Jessica Bibbee <> wrote:

4. Building the UI - review Michael Gettes' recent experience
( )

. API - UI - gsh relationship and multiple builds and multiple tomcats

One way of sharing `single` API and UI installations among multiple environments is to make use of symbolic links in Unix. There are very few core files which need differ between environments:

Grouper API:
Contents of conf, particularly:

Grouper UI:

I would envisage a utility script e.g. ginstall, which is configured with a working directory e.g. grouper-instances, and the location of grouper and grouper-ui.

`ginstall create mlist` would create:


and symlinks to other files/directories in grouper and grouper-ui

`ginstall mlist` would cd to the particular instance and might put gsh on the path and modify your prompt.

In this way, the main parts of grouper and grouper-ui are shared, but configuration files can be modified for particular environments, and it would be easy to switch between environments.

Currently has hard-coded paths set at build time, however, it will be possible to overcome this i.e. provide GROUPER_CONF in the environment.


GW Brown, Information Systems and Computing

Archive powered by MHonArc 2.6.16.

Top of Page