Permalink
Browse files

add a note about "rubygems-bundler to generate wrappers aware of noexec"

  • Loading branch information...
mpapis committed Apr 2, 2012
1 parent 8d05e5f commit 99c7d63f35ae75437c70774ac86aa520ec1ea434
Showing with 13 additions and 0 deletions.
  1. +13 −0 README.md
View
@@ -12,6 +12,19 @@ Then, in your .profile (or somewhere you can set env variables)
And you're done!
+Alternatively you can use rubygems-bundler to generate wrappers aware of noexec, install:
+
+ gem install rubygems-bundler
+
+change a line in ~/.gemrc to:
+
+ custom_shebang: $env ruby_noexec_wrapper
+
+and run (once):
+
+ gem regenerate_binstubs
+
+
## Configuration
Though you can let noexec do it's own thing and rely on looking up your binary via your Gemfile, you can also specify which binaries you want included or excluded. Create a .noexec.yaml file along side any Gemfiles you want to use. Then, to enable (or disable) the usage of your particular binary into your bundle, add an include or exclude section. For example:

0 comments on commit 99c7d63

Please sign in to comment.