I am using Linux to manage many versions of Perl on Fedora notebooks. I have used it to run command line scripts with great advantage, which mostly use.
Now I want to move the written web applications using various PRLS installed in my $ HOME
. I'm familiar with using Perl web applications in $ HOME
s for using Apache's user_dir
or creating a virtual host, but in a clean way to integrate it and Perl Break I'm unable to manage managed Pearl especially I need help understanding and getting answers to these questions:
- How to install perlbrew under mod_perl?
- It is assumed, how can I configure my VirtualHost so that it turns the correct Perl that is current?
- If this is not possible, (which I suspect) can I use at least local establishments to run vanilla?
Thank you for your attention.
I do not think this is a good use for Perl Book, which is simple Runs around The move is around the mod_perl module switch. Remember, mod_perl is going to be binary-incompatible between major versions of Perl, and you have to compile it with Apache to use every Pearl (and Apache).
perlbrew actually does two big things for you:
- Install Pearl, which is easy for you to do.
- Switches around the symlink, so
perl
whatever you want is the version.
If you leave that last one, then Perlbri is not actually doing so much for you. I do not think the symlink feature is particularly valuable.
I think that Perlbuy is fine for what it is, but when you start working outside your limited range, then there is no time to use it. This is considered to be a tool to save you some time and headache, so if that goal is not meeting, then this is not the right tool for your situation.
In this situation, where I am supporting a single single, large web application, I give it my own perl installation that I do not allow anything else to be used.
Accessories should not be configured. If you are using mod_perl, then Pearl already exists and you do not get to choose a Pearl. If you are using CGI accessories, you specify Pearl on the Shebeel line. You have to make sure that Apache chooses the correct library directories, but I think that Perbbluh handles it that you may have to use something like SetEnv
or your httpd.conf.
For vanilla CGI, just point to the correct (symlink) path, whatever the default perlbug version, the CGI program will only use that path that indicates that path.
Comments
Post a Comment