I have noticed some strange behaviour with locating resources to do with 
the location of the Mojo libraries.

If the Mojo and Mojolicious library directories are in the same location on 
the disk then everything is fine

ls -l
total 18
drwxr-x---    2 dar99    UsersGrp        96 Jun  2 16:58 Getopt
drwxr-x---   13 dar99    UsersGrp      1024 Jun  2 16:58 Mojo
-r--r--r--    1 dar99    UsersGrp      4016 Jun  1 10:02 Mojo.pm
drwxr-x---    2 dar99    UsersGrp        96 Jun  2 16:58 MojoLegacy
drwxr-x---    9 dar99    UsersGrp      1024 Jun  2 16:58 Mojolicious
-r--r--r--    1 dar99    UsersGrp     23216 Jun  1 10:02 Mojolicious.pm
drwxr-x---    2 dar99    UsersGrp        96 Jun  2 16:58 Test
drwxr-x---    3 dar99    UsersGrp        96 Jun  2 16:58 auto
-r--r--r--    1 dar99    UsersGrp      4908 Jun  1 10:02 ojo.pm

[Wed Sep 17 16:56:17 2014] [debug] GET "/adadasd".
[Wed Sep 17 16:56:17 2014] [debug] Template "not_found.development.html.ep" 
not found.
[Wed Sep 17 16:56:17 2014] [debug] Template "not_found.html.ep" not found.
[Wed Sep 17 16:56:17 2014] [debug] Rendering inline template 
"569839bd27413e47e26c8476bacb2540".
[Wed Sep 17 16:56:17 2014] [debug] Rendering inline template 
"4fcf2af99f1803a7a26c2e9b04430f8c".
[Wed Sep 17 16:56:17 2014] [debug] 404 Not Found (0.035334s, 28.301/s).

However if the Mojo module directory is in a different directoryto the 
Mojolicious directory then I get the following error:

total 17
drwxr-x---    2 dar99    UsersGrp        96 Jun  2 16:58 Getopt
drwxr-x---   13 dar99    UsersGrp      1024 Jun  2 16:58 Mojo
-r--r--r--    1 dar99    UsersGrp      4016 Jun  1 10:02 Mojo.pm
drwxr-x---    2 dar99    UsersGrp        96 Jun  2 16:58 MojoLegacy
drwxr-x---    2 dar99    UsersGrp        96 Jun  2 16:58 Test
drwxr-x---    3 dar99    UsersGrp        96 Jun  2 16:58 auto
-r--r--r--    1 dar99    UsersGrp      4908 Jun  1 10:02 ojo.pm

ls -l
total 15
drwxr-x---    9 dar99    UsersGrp      1024 Jun  2 16:58 Mojolicious
-r--r--r--    1 dar99    UsersGrp     23216 Jun  1 10:02 Mojolicious.pm


[Wed Sep 17 16:59:13 2014] [debug] GET "/adadasd".
[Wed Sep 17 16:59:13 2014] [debug] Template "not_found.development.html.ep" 
not found.
[Wed Sep 17 16:59:13 2014] [debug] Template "not_found.html.ep" not found.
[Wed Sep 17 16:59:13 2014] [debug] Template "not_found.development.html.ep" 
not found.
[Wed Sep 17 16:59:13 2014] [debug] Template "not_found.development.html.ep" 
not found.
[Wed Sep 17 16:59:13 2014] [debug] Template "not_found.html.ep" not found.
[Wed Sep 17 16:59:13 2014] [debug] Template "not_found.development.html.ep" 
not found.
[Wed Sep 17 16:59:13 2014] [debug] Nothing has been rendered, expecting 
delayed response.

If I explictly add the templates and public directories to the renderer and 
static paths then everything works as expected. However, this doesn't help 
with the PODRender which generates the following error:

[Wed Sep 17 17:09:05 2014] [debug] GET "/perldoc".
[Wed Sep 17 17:09:05 2014] [debug] Routing to a callback.
[Wed Sep 17 17:09:05 2014] [debug] Template "perldocmodule.html.ep" not 
found.
[Wed Sep 17 17:09:05 2014] [debug] Template "not_found.development.html.ep" 
not found.
[Wed Sep 17 17:09:05 2014] [debug] Rendering template "not_found.html.ep".
[Wed Sep 17 17:09:05 2014] [debug] 404 Not Found (0.263153s, 3.800/s).

We have a couple of different projects that use Mojolicious, some of them 
are Web based and some of them just use the Mojo modules for the IOLoop 
functionality. To reduce the number of unnecessary files transferred during 
deployments we split them up, but now we have this problem.
Since some of our hosts are currently running Perl 5.8 we are using version 
5.01 (Tiger Face).

-- 
You received this message because you are subscribed to the Google Groups 
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.

Reply via email to