-
Notifications
You must be signed in to change notification settings - Fork 1.2k
bumping connect-mongo broke openshift deploy #1844
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
Comments
Mmm, this is because of the quite old Node version you & Openshift are using. For now I'd suggest re-installing the latest connect-mongo and importing |
Ideally openshift would have a more up to date version of Node, I run 4.x locally but alas community managed deployments are a ways behind. Thanks for the advice. |
@unsalted would adding something to the readme about updating the node version in Openshift help? I found this article: https://blog.openshift.com/any-version-of-nodejs-you-want-in-the-cloud-openshift-does-it-paas-style/ |
@Awk34 I suppose it would be, I will have to look into how that would work with the app deployment, as you know when using buildcontrol it decides the node module it deploys as. Prior to this change I quite literally didn't need to think at all about openshift deployments using angular-fullstack, just let my fingers do the walking and trust that it was configured to work. I could setup an account for a client, deploy to that account and point a dev domain in under an hour which was awesome. BTW angular-fullstack makes my life so much simpler thank you ; ) |
@unsalted I think what I might do for now is include |
Bumping the version of connect-mongo creates an error on fresh deployment to openshift.
Bringing the version back fixed the problem.
Here is potential issue #1782
Openshift Log:
The text was updated successfully, but these errors were encountered: