The README says:
* Download phpCAS from http://www.ja-sig.org/wiki/display/CASC/phpCAS
This link is now dead. It seems that
https://wiki.jasig.org/display/CASC/phpCAS
is the new location for download information, with
http://downloads.jasig.org/cas-clients/php/current.tgz
being the thing to get.
Here's a quick keylog, that may be handy to add to INSTALL.txt
export LIBRARIES=sites/all/libraries
if [ ! -d "$LIBRARIES" ]; then
mkdir $LIBRARIES;
fi
cd $LIBRARIES
wget http://downloads.jasig.org/cas-clients/php/current.tgz
tar -xz -f current.tgz
# rename to remove the version
mv CAS-* CAS
Comments
Comment #1
dman commentedI wanted to add a makefile too, to ease automated deployment (single-sign-on + a garden of aegir sites is a natural fit) but the download package doesn't want to allow itself to be renamed.
cas.make
.. not quite good enough.
I get
Anyone know how to get around that? Also, the PHPCAS package is a (very small) tarbomb, but mostly harmless.
Comment #2
bfroehle commentedI committed a fix for the download link locations in 6.x-3.x and 7.x-1.x.
I'm not sure what to do with the drush makefile. I need some more guidance here.
Comment #3
bfroehle commentedWell one option would be to grab phpCAS from the github source --- https://github.com/Jasig/phpCAS/tree/master/source.
Comment #4
dman commentedTrue, could try that I think.
On experimentation, seeing as the config page allows you to choose the path - it's still possible to enter the extra path manually, so it's not terrible.
But It's still one step away from being 100% automatic and magic.
Grabbing the git requires the user machine to have git installed - might be 50/50 on a non-dev deployment server...
Comment #5
bfroehle commentedIncidentally, if phpCAS didn't include that package.xml file, your provided drush make file would work fine. :(
Comment #6
bfroehle commentedI'm marking this as fixed -- a drush make file would be convenient, but there does not seem to be any way to get it to work.
I've added a simplified version of your shell directions to the CAS Documentation and the README.txt file.
Comment #7
dman commentedCoolio.
Yeah, makefile only if it did exactly what was promised, I agree.
Comment #8
jdschroeder commentedThis may not be exactly what you're looking for, since it's not contained to the makefile, but it's a good enough workaround for my needs.
I'm using a bash script that accepts some arguments for quick deployments. As part of that script,
drush makeclones phpCAS from Github and then within the libraries folder creates a symlink along the lines ofln -s phpCAS/source CASComment #9
dman commentedI'm actually doing it with a makefile + a feature, as the reason I wanted to automate the download also included pre-configuring the address of my CAS server for distributing a package.
I use strongarm to define the CAS library path (with the extra subdir), and also the CAS URL.
That was the goal I needed to get to anyway.
So it all comes together OK :-)
Comment #12
jon pughphpCAS is now available on github: https://github.com/apereo/phpCAS
Makefile to load it into the correct location is as follows:
Also on packagist, so you can include in composer.json: https://packagist.org/packages/apereo/phpcas