Supporting Open Source Software for Education
March 30, 2010
Comments: 0
by mdesimone
We've come up with a way to deploy different instances of the KFS (such as test, production, and development) such that only the production deployment is configured to use the production CAS, while dev & test use the builtin CAS that comes with KFS. Most institutions want single sign-on in their production system but not in their test or development system. At San Joaquin Delta College we've addressed the differing CAS configurations by creating multiple versions of the source code file in which CAS is configured (web.xml). The build uses a different file depending on which instance is being built. This approach has saved us a lot of time because we don't have to change the code in this file each time we build.
Mike DeSimone
Sr. Technical Consultant
rSmart