Please explain (in docs) how to create apache configs properly about mojo

[kraih]

The wiki might be of help. (https://github.com/kraih/mojo/wiki/Apache-deployment)
But patches are always welcome.

[xbergade]

Using ScriptAliasMatch /* /home/dimka/work/test/test.mojo instead of ScriptAlias / ... in the Apache config solves the 404 problem, unfortunately Mojolicious::Lite then seems to get confused and only the / route gets triggered, regardless of the URL. To get around that, add a $ENV{'SCRIPT_NAME'} = '/' before your app->start('cgi') line, as per Sergey Sinkovsk tip.

I'm 99% sure this used to work fine without the ENV hack during the 0.99XXX series, seems that with v1.01 the ENV hack is required.

[kraih]

That might be fixed in 1.02.

[xbergade]

It's not fixed in 1.1, and worse: the 1.01 hack doesn't work anymore!
It seems that mojo in that configuration is completely ignoring (or not using?) the REQUEST_URI or SCRIPT_NAME env keys, which are (in my tests) both clearly set to the URL, so I'd expect the route subsystem to kick in.

Has anyone found other workaround for 1.1?
Is the original example above not the proper way to do it under Apache?

[xbergade]

Still broken under 1.11 :(

[xbergade]

Found a workaround under 1.11, use this instead in the Apache config:
ScriptAliasMatch /(.*) /home/dimka/work/test/test.mojo/$1

[kraih]

I don't see anything broken in Mojolicious, just a normal Apache configuration problem.

[xbergade]

The key is that ScriptAliasMatch /* /home/dimka/work/test/test.mojo used to work fine before the 1.0 series, without any hacks. I guess Mojolicious was using one of the ENV values to figure which route to trigger. Under v1.0+ this no longer works and the workaround is to use ScriptAliasMatch /(.*) /home/dimka/work/test/test.mojo/$1 in the Apache config so that Mojolicious can figure out which route to use.

[kraih]

Without a real unit test there is not much i could do, you might even have depended on a bug.