Skip to content
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

Purpose of handler #27

Open
leonelgalan opened this issue Jan 29, 2015 · 4 comments
Open

Purpose of handler #27

leonelgalan opened this issue Jan 29, 2015 · 4 comments

Comments

@leonelgalan
Copy link
Contributor

What's the purpose of rehash rbenv? Rehash is called manually from tasks/main.yml:151 or tasks/main.yml:182

It it notifies the handler instead, we could install gems (env: system so now default gems plugin available) and rbenv rehash would happen at the very end.

@zzet
Copy link
Owner

zzet commented Feb 24, 2015

@leonelgalan this issue is actual now?

@leonelgalan
Copy link
Contributor Author

Yeah, but I discovered that handlers are only "triggered" at the end of the playbook's run. So if we install bundler, we need to manually rbenv rehash in order to have bundle available before the playbook finishes.

I wish there was a handler-like task that could be triggered at the end of the recipe's run or manually for DRYness. So it's might be a non-issue.

@zzet
Copy link
Owner

zzet commented Feb 25, 2015

I have nothing against to run rehash immediately after installation bundler. I think it is a true way.

@zzet
Copy link
Owner

zzet commented Feb 25, 2015

If you think that should be divided rbenv global {{rbenv.ruby_version}} & rbenv renash - I think that this can be done. Essentially it will not change, but it will be obvious.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants