As of Perl 5.26, the current directory isn't in @INC any more, regardless of taint mode

So, I am getting the point that taint, and later versions of Perl are trying to make it difficult to use relative paths for modules!

This raises a different question...
Where should the modules be located?

If there was just one 'version' or environment of the website then it would be easy to just put them somewhere above the website root in the filesystem. I do this with modules that are common to all my websites. But there are always 2 and sometimes 3 different environments for every website. Production, test and sometimes development.

/home/myusername/somewebsite/prod/cgi-bin/Site/
/home/myusername/somewebsite/test/cgi-bin/Site/
/home/myusername/somewebsite/dev/cgi-bin/Site/

[download]

Having the modules in a relative path allows them to be logically separated in each of the environments and to be developed and tested before being released into production.

Is the solution to locate the modules above the website root with a different subfolder for each environment? 

/home/myusername/somewebsite/prod/cgi-bin/
/home/myusername/somewebsite/test/cgi-bin/
/home/myusername/somewebsite/dev/cgi-bin/
/home/myusername/somewebsite/perlmodules/prod/
/home/myusername/somewebsite/perlmodules/test/
/home/myusername/somewebsite/perlmodules/dev/

[download]

I tried this for template files on the first site I created using Template. It was a bit messy to maintain so instead, for future projects, I have stored the templates in under the webroot but protected from HTTP access by putting an index.html file in the directory which sends the user to the homepage.

Is there a better way to handle this issue - what is the accepted norm for locating Perl modules on a webserver where there are multiple sites and multiple environments within each site?

In reply to Re^2: Using relative paths with taint mode by Bod
in thread Using relative paths with taint mode by Bod

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.