Shibboleth Developers

["RL 'Bob' Morgan" <>]

On Wed, 18 Jun 2003, Scott Cantor wrote:

> Well, what I was doing was:
>
> I unpack the origin tarball in /opt
> I create /opt/shibboleth-origin-1.0/conf
> I copy all the default config files into conf
> Then I change origin.properties in the webapp to point out to there with
> file:// URLs

Right, I was doing the same, more or less, which is how I got confused
since origin.properties still has to be in the original spot.

> This is pretty workable for updates as far as just reducing it to
> maintaining origin.properties across updates. You still have to trash
> the old tree to get the new one to unpack.

"trash" meaning what exactly?  Like I say, when I just moved
webapps/shibboleth/ to somewhere else, tomcat wouldn't start, so I just
reinstalled tomcat, which is a pain given jk setup, endorsed, etc.

> Walter pointed out that the better way is to turn off Tomcat's expansion
> of warfiles, and basically maintain the config inside a build tree of
> the source. Then you just change or update it, run ant, copy the
> dist/war over, bounce, and done.
>
> I like that a lot.

Ummm, is this a solution for ordinary sysadmins (who just want to install
binaries), or just developers?  Sounds like the latter.

 - RL "Bob"


------------------------------------------------------mace-shib-design-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

------------------------------------------------------mace-shib-design--