If you have virtual servers you could always create a separate prefix for the webapp. Then you compile and install perl into the prefix. You can usually get better performance from compiling your own perl (ie without threads.) Another plus is you don't have to worry about upgrading the system perl harming your webapp.

You could then tarball up the whole thing and not worry about the "crust" and "filling". Or make the whole "crust" from scratch on the next machine and only tarball the filling... your Catalyst app. This takes a little longer to compile everything but is very straightforward and like I said you have less to worry about in the future.

I think this is analogous to what CountZero and Your Mother have said. I like compiling perl as well because XS modules (ie Class::MOP) won't break on a major system perl upgrade.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.