Document environment variable expansion in configuration #5181
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added documentation on using environment variable expansion for configuration values, including examples.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that I can use variable expansion within
php-fpm.conffiles. The documentation page does not explicitly mentions this. Instead it only provides examples of passing environment variables on to the child process.At the very top of the page there is a mention that
php.inisyntax is used. This somewhat implies that variable expansion is supported just like inphp.ini. I suggest though that we update the discussion on environment variables with an example of how it php-fpm can be configured using env vars to make the support for this more explicit.