Date: Thu, 28 Apr 2016 12:51:29 +0200 From: Luca Ferrari <fluca1978@infinito.it> To: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Why is www's $PATH only /usr/bin:/bin? Message-ID: <CAKoxK%2B7n0PZsqAtZAG-R_VsXmxZwC0iKafqzM6Hkh8LnZNY6Vg@mail.gmail.com> In-Reply-To: <20160428094002.GA43096@box-fra-01.niklaas.eu> References: <CAKoxK%2B41i=viH9qy-KrnwoioRXwv7U2FYNtP8B-AQW-RmVc_6w@mail.gmail.com> <20160427082142.fd56427e6b96fb6fb2b29035@sohara.org> <20160427133304.319a997b@gumby.homeunix.com> <20160427120704.GA77440@becker.bs.l> <20160428094002.GA43096@box-fra-01.niklaas.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 28, 2016 at 11:40 AM, Niklaas Baudet von Gersdorff <stdin@niklaas.eu> wrote: > In NGINX's configuration it's possible to change php.ini settings for > particular server processes. I'll go for that. If that's not possible I'll try > to spawn a separate php-fpm process that configured the way I need it. And if > that's not possible I'll hardcode a function in PHP. Another way, less dynamic but I suspect a little more robust, is to use a deployment that creates/adjusts the right path to the right command. For instance you can have a PHP config file with variables that point to commands (full path) and have a deployment script to adjust such values to installations. I use this technique when placing the same application over sligthly different servers. Luca
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKoxK%2B7n0PZsqAtZAG-R_VsXmxZwC0iKafqzM6Hkh8LnZNY6Vg>