[Catalyst] path_to() and symbolic links

marcus marcus.baker at gmail.com
Tue May 9 15:12:56 CEST 2006

That worked out.  I'm kind of dejected I couldn't get away with a work
around that would automagically figure out the application directory,
as we have three different environments (dev/staging/production), so
I'll have to come up with a solution to dynamically set CATALYST_HOME
depending on which server the application is running on, but that
shouldn't be too hard.



2006/5/9, Carl Franks <carl at fireartist.com>:
> On 08/05/06, marcus <marcus.baker at gmail.com> wrote:
> > I'm having issues with path_to() correctly resolving in issues where I
> > access my fastcgi script out of a symlink to the actuall catalyst
> > script directory.
> >
> > Suppose my Catalyst application is in /usr/local/MyApp, and my apache
> > document root is in /srv/www.  If I symlink /srv/www/myapp to
> > /usr/local/MyApp/script and try accessing http://localhost/myapp,
> > path_to() seems to resolve everything relative to /srv/www as opposed
> > to /usr/local/MyApp.
> >
> > Is there a way around this?
> I had the same issue recently, and fixed it with this in lib/MyApp.pm:
>     $ENV{CATALYST_HOME} = '/usr/local/MyApp';
> }
> _______________________________________________
> Catalyst mailing list
> Catalyst at lists.rawmode.org
> http://lists.rawmode.org/mailman/listinfo/catalyst

More information about the Catalyst mailing list