-
Notifications
You must be signed in to change notification settings - Fork 112
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
it is posible to install multiple ruby versions?? #35
Comments
Hi @blackjid! At this moment no. Until April, I will not have time to add this functionality. |
I'd be happy to make a PR... - role: zzet.rbenv
rbenv_users:
- deploy
ruby_versions:
- 2.0.0-p643
- 2.1.2
ruby_global_version: 2.0.0-p643 something like that? |
If we talk about users and the version of Ruby - then we have a matrix: rbenv_users:
- deploy
- other
ruby_versions:
- 2.0.0-p643
- 2.1.2 for deploy and other user will installed all ruby versions from list. I think this is not correct. like as - rbenv_install:
- user: deploy
versions:
- 2.0.0-p643
- 2.1.2 or as hash { rbenv_install: [
{ user: deploy, versions: [2.0.0-p643, 2.1.2] },
{ user: other, versions: [2.1.2] }
]} I need to take a break and think about how best to do this. We should bear in mind that this is a rare case and role overload is not necessary. Most users will want to install 1 ruby version for 1 or more users. If we say that we need to put more than one version, you should talk about what you need or different users on different versions of one or several versions, but at the same time indicate which of them is used by default. For example last defined in versions list, or specify version as key - rbenv_install:
- user: deploy
versions:
- 2.0.0-p643
- 2.1.2
default:
- 2.0.0-p643 In addition, changes in key version may be a surprise to those who already use role. After these changes will be released major version. |
@blackjid If you have any thoughts on this issue - I will be glad to consider them |
Hi @blackjid! I think this definitions is good (based on default settings): rbenv:
env: system
version: v0.4.0
ruby_version: 2.2.0 # For system install only
# ....
rbenv_install:
- user: deploy
ruby_versions:
- 2.0.0-p643
- 2.1.2
default: 2.0.0-p643
- user: other
ruby_versions:
- 2.2.0
- 2.1.2
default: 2.2.0
- user: old
ruby_versions:
- 1.9.3
default: 1.9.3
# or
# rbenv_install:
# - { user: deploy, ruby_versions: [2.0.0-p643, 2.1.2], default: 2.0.0-p643 }
# - { user: other, ruby_versions: [2.2.0, 2.1.2], default: 2.2.0 }
# - { user: other, ruby_versions: [1.9.3], default: 1.9.3 } What do you think about it? |
I like it, |
@blackjid you are planning to prepare PR? |
mm, here is the thing... I offered to create a PR... i know... but I ended up creating a role specific for my use case.... why? I don't need some of the feature of this role, such as multi-user installations, but I need other features besides multiple-rubies such as aliases and per ruby gem installations The thing is that I'd be happy to provide a PR, but i'm not in a hurry now, (I was when I opened the issue) |
What do you mean about aliases? (you can open separated issues for discussion of this features, this issue only for multiple-rubies installation) |
Hey @blackjid @zzet i also had to create my own role to support multiple rubies.. https://github.com/pablocrivella/ansible-role-rbenv |
Hi @pablocrivella . You can send pull request. |
I can implement this FR on weekend |
@UnderGreen it's cool |
Hi @UnderGreen . Do you plan implement this FR? |
👍 |
Any movement on this? |
done |
something like this
The text was updated successfully, but these errors were encountered: