I have a project that involves php and bash scripting.
I want to outsource all user-settings to a file "settings.conf". This file should therefore contain bash-variables aswell as php-variables.
However, bash would find php code quite irritating, aswell as php couldn't cope with bash code.
What would be a best practise to make sure my php script would only take care of the php part of the file and bash would only mind about the bash part?
The settings file might look like this
### Settings-File
## php-settings
<$php
$language = "en";
$url = "http://foo.bar";
$copyright = "Copyleft License";
?>
## end php-settings
## bash-settings
pathToCertainFile="/home/johndo/files/certainFile"
## end bash-settings
## EOF
system('command-here');command, and shells can run PHP with thephp command-herecommand. As for settings? You can set custom php-related settings (override php.ini) in a .htaccess file, and you can make both PHP and bash scripts generate a .htaccess file with contents of your choice. Helpful?$pathToCertainFileor$language). These settings should be edited by the users of my script. However, I want to outsource all setting-variables to just one file.