How would you initialize an Apache app with plenv? about plenv

[lestrrat]

I can't speak for others, but I don't think using plenv for such purposes is a good thing to do.

I use plenv for personal perl copies -- i.e. my Mac that I use everyday, I use plenv so I can switch around versions when necessary.

But for deployed apps, I never use plenv. Instead I use something like xbuild or Perl::Build and stick to that version until I manually decide to upgrade.

[Lx]

I'm interested in this discussion because I had a vaguely similar use case in mind.

I was hoping to run a Plack-served app through a plenv-provided Perl as a regular (but purpose-made) user on a Debian system, started by a Daemon::Control-prepared init script at system boot.

Everything works fine when run from that user's shell, because obviously the environment provides the means to pick out the right Perl.

At the init level though, the system Perl is run and none of the dependencies are available, so nothing starts.

There doesn't seem to be an easy fix to this. Is the only solution to prepare a Perl exclusively for that web app (probably using Perl::Build) and then hard-code all of the web app's scripts to use that Perl (which would have the effect of tightly coupling the two)?

Thanks in advance for any pointers.

[lestrrat]

In real life we often have a wrapper script that wraps any command we execute:

./scripts/env.sh ./scripts/foo.pl

and in that script we do something similar to

export PATH="/path/to/perl-that-we-should-use-for-this-project:$PATH"
export PERL5LIB="/path/to/project/local/lib/perl5:/path/to/project/lib"
...
exec "$@"

Then your shebangs just need to be

#!/usr/bin/env perl

or something similar

[Lx]

That sounds like exactly what I need in my case: make the code "Perl-agnostic" (for lack of a better term), and make whoever runs it responsible for making the environment point to the right Perl. No plenv required, and everything is nicely decoupled. Thanks very much for your insight.