sensu/sensu-docs — pull request #141 by edzhelyov (2014-10-06 15:50:57+00:00)
Title: Add information about the EMBEDDED_RUBY when adding the first check

Hi,

I just started using Sensu a day ago and got confused when I got to the point where the first check is added.
Basically on a vanilla installation using the omnibus package the plugins won't work because they will use the environment ruby. I moved forward by editing the plugin shebang, but then when I was looking for production ready checks I found that all the plugins in the community use the system wide ruby.

Asking in the IRC channel about best practice I got a few answers to put the embedded ruby first in the PATH and that EMBEDDED_RUBY option actually does that. I think it's good to have that information here, because if you are new to Sensu this can be a confusing moment as I have the expectation that using the package will prevent such problems.

I did find that EMBEDDED_RUBY is documented in the FAQ just before updating the documentation, but still think it's proper to mention it here.

I'm very new to the project, so I'm not aware of best practices, workflow, etc so I'm open for suggestions about this PR.