#!/bin/bash

# Clear the rbenv setup that has been done in the development repo
# Without this, rbenv won't do the setup again after changing directory,
# and won't pick up the app's ruby version if defined.
unset RBENV_VERSION

cd $1
shift
exec "$@"

#!/bin/bash

cd $1
shift
exec "$@"

--- 
+++ 
@@ -1,9 +1,4 @@
 #!/bin/bash
-
-# Clear the rbenv setup that has been done in the development repo
-# Without this, rbenv won't do the setup again after changing directory,
-# and won't pick up the app's ruby version if defined.
-unset RBENV_VERSION
 
 cd $1
 shift
Fix foreman run script to work with rbenv

Because foreman is starting one ruby process from another ruby process,
the second one was inheriting the parents rbenv setup, and therefore
ignoring the application's .ruby-version file.  Unsetting this env
variable fixes that.
