The better solution, especially from a sanity perspective, is to have (at least) two directory trees. A dev, a prod, and possibly a QA. By choosing which directory you're in your URL and making sure that all your modules are in a different place for each environment, you will save yourself a ton of headaches. Plus, it makes promoting code a lot easier. This is especially true if you use the QA option. You mnake sure everything works in QA like you want, then mv prod to prod_save and copy QA to prod. No crazy variable changes ... no versions to mess up ... just ease of development and maintenance.

Out of curiousity ... what does it do? I've been thinking about writing a simplified Quicken so I can gedt rid of the last Windows machine in the house. It might be an interesting idea to come with a place to advertise useful home apps written in Perl ...

------
We are the carpenters and bricklayers of the Information Age.

The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

In reply to Re: Production / Development on the same server. by dragonchild
in thread Production / Development on the same server. by yosefm

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.