Rather than specify the exact path to PHP in the hashbang line of innreach_check.php and prep_file.php, the env utility can locate it in a cross-platform way. So even if PHP is installed in /usr/local, users won't need to update these files with a different path because env will find them.
This simplifies set up a bit, allowing the removal of one <li> from documentation.php. I see mixed information on the web on whether or not various env implementations can pass flags to the target programs, so if the -e flag is really necessary in innreach_check.php you'd want to test further or consider not using env. I can tell everything works on my OS X laptop but I haven't tested on our Ubuntu servers yet.
Rather than specify the exact path to PHP in the hashbang line of innreach_check.php and prep_file.php, the
env
utility can locate it in a cross-platform way. So even if PHP is installed in /usr/local, users won't need to update these files with a different path becauseenv
will find them.This simplifies set up a bit, allowing the removal of one
<li>
from documentation.php. I see mixed information on the web on whether or not variousenv
implementations can pass flags to the target programs, so if the-e
flag is really necessary in innreach_check.php you'd want to test further or consider not usingenv
. I can tell everything works on my OS X laptop but I haven't tested on our Ubuntu servers yet.