in reply to Best practices for deploying perlbrew and carton with apache fast-cgi
sourcing perlbrew bashrc does'nt give you anything but the advantage to `use` a different version on-the-fly. It is unlkely that you need to do so when launching the app daemon. I would simply put the desired perlbrew-ed version of perl in the $PATH when launching the app daemon.
To automatically do that when rebooting the machine, create a shell script as a wrapper that modify the PATH first, then launch the app, and invoke the wrapper script from crontab (with @reboot time) or init.d.
perlbrew really does not have to be involved unless it is required to run app with multiple versions of perl. Even so, writing multiple wrapper scripts cannot be too difficult. :)
|
|---|