Problems? Is your data what you think it is? | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
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... 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.
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?
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
|
|