expose request path to runOn commands as an environment variable #55
Conversation
This file contains 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
|
merged, thanks, but i'll remove the PathEnvVariable option since 99.99% of users won't need it. |
|
This issue is being locked automatically because it has been closed for more than 6 months. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This patch modifies the
runOnInit/runOnDemand/runOnPublish/runOnReadcallers to set an environment variable with the calling path. (ForrunOnInit, it will be called with the configured path, of course)A
pathEnvVariableconfiguration item is also introduced to specify the name of the environment variable to be used. Its default value isRTSP_SERVER_PATHand there is sanity checking to ensure that the provided name is valid (alphanumeric + underscore, no leading digit).(Addresses #47)