Set a GEM_PATH variable in /etc/default/sensu #203
Merged
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.
If we have gems installed in different locations, we'd like to be able to use them without having to mess around the /opt/sensu directory.
We have a use case where we want to install all ruby gems via debian packages, but we don't want to be messing around with the system's gem, or the embedded gem, etc. Would it be possible to extend the module to have this option in
/etc/default/sensu
?I haven't seen there are tests for this, but let me know if there is anything I can do.
Also, I'm slightly confused with
GEM_PATH
andGEM_HOME
. Does the former need to include/respect the latter?Thanks.