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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
