6523 2008-11-04 14:30 configure options for paths and urls need revamp 2009-12-07 19:33:02 1 1 1 Unclassified GridShib GridShib-CA 0.5.1 All All RESOLVED FIXED P3 normal --- 6808 1 vwelch@uiuc.edu vwelch@uiuc.edu gridshib-dev@globus.org vwelch@uiuc.edu 2008-11-04 14:30:58 All the configure options for paths and urls are just overwhelming. I can't keep them all straight. Got to simplify them somehow. Plus needs some checking for default paths for html and cgi, if we use these, make sure they actually exist or force deployer to provide. Don't assume cgi-bin and html are subdirectories off of common root. vwelch@uiuc.edu 2009-10-06 07:25:56 On HEAD: changes committed to simply paths down to one standard web directory and one shibboleth-protected web directory. vwelch@uiuc.edu 2009-11-01 12:42:07 Some simplification on head now. New options below. Removing distinction between html and cgi directories helps. --with-gridshib-ca-url=<url> Specify the URL for the gridshib-ca. This is the relative URL, without hostname, where the main GridShib-CA starting page will be found. (Default: /<gridshib-ca-dir-name>/) --with-gridshib-ca-web-path=<path> Specify the path for the GridShib-CA web space. This is the path that corresponds the the GridShib-CA base URL. (Default: <www-dir>/<gridshib-ca-cgi-bin-url>) --with-shib-protected-url=<url> Specify the base url for the Shibboleth-protected web space. This is the relative URL, without hostname, where Shibboleth-protected webapps are installed. (Default: /shib-protected/<gridshib-ca-dir-name>) --with-shib-protected-path=<path> Specify the path for the Shibboleth-protected web space. This is the filesystem path where Shibboleth-protected webapps are installed. (Default: <apache_docroot>/<shib_protected_url>) vwelch@uiuc.edu 2009-11-01 12:48:22 Still need to do the following before resolving this: Plus needs some checking for default paths for html and cgi, if we use these, make sure they actually exist or force deployer to provide. vwelch@uiuc.edu 2009-12-07 19:33:02 (In reply to comment #3) > Still need to do the following before resolving this: > > Plus needs some checking for default paths for html and cgi, if we use these, > make sure they actually exist or force deployer to provide. Err. Easier said than done. Depending on configuration options we may or may not be using APACHE_DOCROOT. Other directories may be created for us by install.sh so it's really hard to detects bad directories prior to installation. Punting on this and considering this bug as completed.