-
Notifications
You must be signed in to change notification settings - Fork 23
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
App is still started with node 0.10.25 after fresh deployment #2
Comments
i have same issue |
Hi, I have the same problem. Any idea or workaround? Thanks. |
Until this is solved, have a look at this auto-updating Node.js cartridge. |
Thanks Icflorescu. It works for me. |
I'd be interested in getting this fixed if possible, thanks. |
I found a workaround. the cartridge is calling a nodjs_context() function before launching node. My workaround was to edit .openshift\lib\utils and add How it looks after the edit: .openshift\lib\utils # Add the node binary path to the PATH.
export OPENSHIFT_NODEJS_VERSION=0.6
export PATH="$node_bin_path:${PATH}" I can't assure that there is no side effects, but my app is now running on node v0.12 |
Thanks @Spouwny. That did the trick for me. I'm running v5.1.0 just fine now. |
@Spouwny worked for me too. I mistakenly set |
@Spouwny - works for me, cheers. |
I need to install the latest version of nodejs and mongodb |
Thanks All! I had originally posted this content as a quick hack to demonstrate how someone could provide their own custom runtime on OpenShift (V2) using the I'd recommend trying @icflorescu's openshift-cartridge-nodejs in the future, since it offers a cleaner separation between the application sources and the javascript runtime. |
Looks like there is a problem with PATH. App starts with 0.10.25, but
node --version
via SSH reports 0.12.0... Maybe OpenShift has changed something?To reproduce:
rhc app create nodeapp nodejs --from-code=git://github.com/ryanj/nodejs-custom-version-openshift.git
console.log('VERSIONS', process.versions);
toserver.js
, git push.rhc tail
output after pushing:The text was updated successfully, but these errors were encountered: