-
Notifications
You must be signed in to change notification settings - Fork 10
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
Possible to upgrade to newer version of iojs? #6
Comments
Currently - no. io.js was moving very quickly when I created this cartridge and wanted a bit more fine control over which version was used. It is starting to slow down / stabilize so I might move to resolving versions on the gears in the very near future. |
ok. I'll leave this open for the moment as a reminder. Feel free to close if you prefer. |
@connyay seeing as Node.js v4 is about to go live (which is the convergence of io.js and Node.js), any chance of bumping to v4? Ref: nodejs/node#2522 |
@IWhitfield Once v4 is out of RC I will bump. I have been mashing F5 so don't you worry 😁 |
Decided to split v4 to a new repo can be found here. |
@IWhitfield if you decide to try out node4 pay careful attention to env variables |
Node.js v4 is running here: http://node4-connyay.rhcloud.com/ |
there's still a need for easy version upgrade with the new node4 as well. |
More of a question than an issue. Readme mentions ramr/nodejs-custom-version-openshift which provides a technique for doing this with nodejs. Does this also work with this cartridge? I might be interested in upgrading to 3.0.0 if so.
The text was updated successfully, but these errors were encountered: