Re: [Catalyst] on the topic of PAR file distribution, why is it frowned upon?
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 tried Shipwright? Rob ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] catalyst.pl-generated installer installs MyApp/root in same dir as MyApp/lib/*?
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 File::ShareDir (which I perused after reading on dhoss's blog about where he's thinking of putting the helper templates), I read that static data for modules are supposed to go in the module's 'auto' directory. Link: http://search.cpan.org/~adamk/File-ShareDir-1.00/lib/File/ShareDir.pm So, if I understand rightly, shouldn't the MyApp/root be going into blib/auto/MyApp/root instead of blib/MyApp/root ? Rob ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Best practice: How to build app parts reusable?
Matt S Trout wrote: Just have your controller base class set: $c->stash(additional_template_paths => $self->template_paths); Can you do something similar if using Mason? Rob ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] catalyst.pl-generated installer installs MyApp/root in same dir as MyApp/lib/*?
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 you're doing automatic continuous integration testing, or automatically building local::libs or debian packages for deployment on lots of machines, you've got to have some kind of automation for dependencies. Rob ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] "featurizing" a catalyst app
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 cursorily, that doesn't seem to be
supported right now. Can somebody who knows what they're talking about
(i.e. not me) confirm?
Rob
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
