[chora] Stable Chora Build

[zx at bugsbunny.laudanski.com]

On Fri, 18 Jul 2003, Chuck Hagenbuch wrote:

I've tried your suggestion from below, and then the page could not be 
loaded.  Here is what I had...

> Quoting zx at bugsbunny.laudanski.com:
> 
> > I think I've set it up correctly.  Here is a snippet:
> >
> > $this->applications['horde'] = array(
> >     'fileroot' => dirname(__FILE__) . '/',
> >     'webroot' => '/horde',
> >     'initial_page' => 'chora/cvs.php',
> >     'icon' => '/graphics/home.gif',
> >     'name' => 'Nuke Cops beta-NC CVS Repository',
> >     'allow_guests' => true,
> >     'status' => 'inactive',
> >     'templates' => dirname(__FILE__) . '/../templates',
> >     'cookie_domain' => $_SERVER['SERVER_NAME'],
> >     'cookie_path' => '/horde',
> >     'server_name' => $_SERVER['SERVER_NAME'],
> >     'server_port' => $_SERVER['SERVER_PORT']
> > );
> >
> > $this->applications['chora'] = array(
> >     'fileroot' => dirname(__FILE__) . '/../chora',
> >     'webroot' => $this->applications['horde']['webroot'] . '/chora',
> >     'icon' => $this->applications['horde']['webroot'] .
> > '/graphics/chora.gif',
> >     'name' => 'betaNC-CVS',
> >     'allow_guests' => true,
> >     'status' => 'inactive'
> > );
> 
> 
> Why are you aliasing chora, if it's in the docroot? Try setting the webroot for
> horde to /horde, the webroot for chora to '', aliasing /horde to /www/horde,
> and leaving /www/horde/chora as the docroot? Make sure you adjust the graphics
> paths, etc. accordingly.
> 

I commented out the alias.  I got that from the FAQ you pointed me to 
earlier.  It was showing that as an example for horde and imp.  These 
settings caused the site to be down completely.

I tried chora webroot to "/../chora" and "../chora" and "chora" with no 
luck.  I also tried horde fileroot to "/.." with no luck.  And I tried 
horde's initial page to "/chora/cvs.php" also to no avail.

:(

-- 
Sincerely,

Paul Laudanski / Zhen-Xjell

[This message is for the designated recipient(s) only and may contain privileged or confidential information.  If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.]