-
-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix for #16, load rbenv environment after install #42
Conversation
I am using your fork but I still have the same issue. It fails randomly, I dont know why. Here is my rbenv recipe include_recipe 'ruby_build'
include_recipe 'rbenv::user_install'
version = node['ruby']['version']
rbenv_user = node['rbenv']['owner']
rbenv_ruby version do
user rbenv_user
action :install
end
rbenv_global version do
user rbenv_user
action :create
end
rbenv_gem "bundler" do
rbenv_version version
user rbenv_user
action :install
end and this is my Berksfile site :opscode
# External cookbooks
cookbook 'apt'
cookbook 'database'
cookbook 'rbenv', git: 'git://github.com/apptentive/chef-rbenv'
cookbook 'imagemagick'
cookbook 'nginx'
# Local cookbooks
cookbook 'set_locale', path: 'config/chef/cookbooks/set_locale'
cookbook 'postgresql_server_utf8', path: 'config/chef/cookbooks/postgresql_server_utf8'
cookbook 'rails_env', path: 'config/chef/cookbooks/rails_env' this is the exception I get sometimes. The bizarre thing is that sometimes it works/
|
@guidomb This is probably because you're not using a login shell for bash executions. Try it with |
@johnbellone but his error is being caused by the rbenv_ruby resource. If @guidomb Did you ever end up solving this? My recipe essentially looks the same as yours. |
@fnichol can you take a look at this and merge if it looks like the right approach? |
Merge current finchol into master
This would add the paths mentioned above into the Chef running process' |
Fix for #16, load rbenv environment after install
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Fixes #16, such that the environment is loaded after install and available for subsequent gem installs