mrvautin
Updating to new versions
We have 2 instances of openKb running on Ubuntu under PM2. To upgrade in the past we have always backed up the data, re configured a new up to date instance and then added the data back in.
Is there an easier cmd line way to do this?
Thanks and sorry for being a n00b :smile:
I could add an NPM script to automate some of the steps and pull changes from GitHub but the real question is... "How much do you trust me?". The issue I see is that I don't have many testers (basically only you) and the code is changing quite a bit lately. I would want to break something you rely on with an update I didn't test properly or don't have an environment to test on (I only test on a OS X).
It's a really good question though. Maybe I will look into it further where you can grab the changes from GitHub, test it's working then run this script to update your two instances? Does that sound like something you would want?
That might be a solution, it just seems a long way at the moment to update to the latest release. Maybe once a release is confirmed as stable it should be published as a major /minor version and then have the option to update in the app?
Fair call. Maybe we can start with this version.
As the chief tester, you can let me know how this version goes. 😉
Sounds like a plan ;) I'll spin up a new one this afternoon and test out all I can.
This looks cool: https://www.npmjs.com/package/auto-updater
Will have to see if it can omit files/folders. Eg: /data and /routes/config.js.
Wonder if it can delete removed files too.
@mrvautin That would be a way of doing it so long as we could preserve certain files / folders.
Hi guys, if you need additional testers or help feel free to leave me a line. Learning node.js but have a background from .net and testing.
I'm also interested in any input on how to manage updating this application while maintaining my own custom changes. In my case an Azure AD SSO. I'm also coming from a .net background and am not sure the best practices and tools for how to do this in node.
I'm also new to nodejs and would like to know about application updates. I heard about pm2 might be worth looking into: https://github.com/Unitech/pm2/
Hämta Outlook för iOShttps://aka.ms/o0ukef
From: J.D. Cain [email protected] Sent: Wednesday, August 2, 2017 4:12:22 AM To: mrvautin/openKB Cc: Kristoffer Gustafsson; Comment Subject: Re: [mrvautin/openKB] Updating to new versions (#68)
I'm also interested in any input on how to manage updating this application while maintaining my own custom changes. In my case an Azure AD SSO. I'm also coming from a .net background and am not sure the best practices and tools for how to do this in node.
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/mrvautin/openKB/issues/68#issuecomment-319548279, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABAeUvIkAo6VGiZOx5o7kpWH9M8GQSr-ks5sT9sGgaJpZM4JxTaG.
It's not super easy which is why I gave up on it. If you look at other major Node.js projects like Ghost (blog app), they introduced a CLI to install and update Ghost blogs. I've tried it and it's pretty hit and miss too.
I ended up doing a fork then using that fork as the upstream for a repo in vso, then doing my best to keep any code changes I'm doing in different files while applying any more general changes in the fork first.