Hey folks:

I'm in the midst of a new product launch 'on the cheap'. I just turned beta over to the stress-testers. Next I need to set up a sandbox where development on the next version can continue.

Problem is, beta is kept up to speed with a make; sudo make install and my sandbox will, for economic reasons, have to live on the same server as the production version, currently beta.

Obviously, I ought to set up a parrallel set of configuration files, templates and logs for the sandbox.

But if in my sandbox, I use a use lib qw( path/to/sandbox/lib ); in my sandbox scripts, what else might I need to do to ensure that my sandbox reads ONLY my sandbox code and doesn't go poking around the site libraries for the modules under development? I only want to separate out the code I'm writing and would prefer that the dependencies be accessible in the site libraries without having to reproduce all of those in a parrallel installation.

All ideas are appreciated.

-- Hugh

UPDATE:

Thanks, perrin, but that actually was not my concern. I was more interested in preventing dev.myapp.com loading the code available in the site libraries on the server instead of the dev/lib branch where the unstable stuff is being tested.

If I did a sudo make install, won't @INC give preference to the site libraries over anything I might offer in my development tree? How do I let it find DBI, etc. in the site libraries and My::App at sandbox/My-App/lib ???

perldoc says: "It is typically used to add extra directories to perl's search path so that later use or require statements will find modules which are not located on perl's default search path."

My question is this: what if those modules ARE available on perl's default search path? If so, how do I control the precedence in which the options are considered?

I assume that the @INC array is walked until the requested module is found. If that is correct, does use lib '/path/to/my/sandbox/lib'; append or prepend the new path to the array?

if( $lal && $lol ) { $life++; }

In reply to Seek ideas for hosting a sandbox on production server . . . by hesco

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.