I've actually had pretty good results deploying my web apps with
Shipwright. The docs and the code are rough, but it actually works
pretty well.
It sputters a bit on configure-requires and on some of the stranger
cases of dependencies, but sounds like it works better than PAR.
Anybody else
Rodrigo wrote:
But how about the /root part? Can mixed-up root dirs be seen as a
single root dir easily?
I'm interested in making a pluggable app as well. Seems like you and I
would want the ability to specify an arrayref for MyApp-config-{root},
and have that work. Poking around
Hans Dieter Pearcey wrote:
This is so strange to me; I *always* install my applications with make install,
or make debian packages of them, or...
Ditto. For me, the most important aspect of actually doing an
installation is having dependencies get pulled in automatically. For
example, if
The Module::Install code generated by catalyst.pl puts MyApp/root into
blib/lib/MyApp/root, right alongside all the things from MyApp/lib. Is
this actually the Right Thing to do? Seems fishy to put the templates
and images and such in the same place as the perl modules.
In the pod for
