@mstan — sorry that you haven't received a response.
NodeBB doesn't save the Mongo database anywhere specific on the file system, it would be wherever the insulted MongoDB install saves it's data.
Following the docs, the "git checkout v1.x.x" doesn't work because it slams me all the way from v1.0.0 to v1.4.<something>. Trying to do an upgrade says stuff like "your database is too far out of date, did you skip a major version"?
And unfortunatly, I have to start with 1.0 because if the importer not supporting anything beyond 1.0.
I read somewhere that you should jump from terminal patches of the previous branch.
So.. like '1.0.0 -> 1.0.4 -> 1.1.0 -> 1.1.x etc..
Is that true? Trying that, though, had a all kinds of problems with version not found issues in Git.
Any guidance would be appreciated.
You can checkout individual versions since they're all tagged.
git checkout v1.0.0 ./nodebb upgrade git checkout v1.1.0 ./nodebb upgrade
That worked well. Thanks!
Follow up question, though. Does that update the plugins along with NodeBB, or is there a separate process for that?
@Eric-Ladner No, it doesn't upgrade the plugins... or I should say, it didn't used to.
More recent versions of NodeBB call
./nodebb upgradePlugins as part of the upgrade process, and that will upgrade plugins (to whatever version nbbpm says they should be upgraded to)...
However, those plugins that aren't registered with nbbpm won't be touched by ./nodebb upgradePlugins.