@julian said in Update from v0.7.0 to v1.4.0:

@PitaJ It shouldn't be impossible though... I've done an upgrade from 0.4.0 era to post 1.x before...

Is it posible directly or just walking step by step through the minor versions?

@alff0x1f said in Update from v0.7.0 to v1.4.0:

You need do in in folder where Nodebb installed. Use cd folder_name

russian: команду надо выполнять в папке, где установлен форум.

Ok. I understand it. But it's not that. It is still the exact same thing "node app --upgrade" inside.

Perhaps anyeone has experience in manual database transfer. It should not be so difficult.

Maybe there is some kind of description of the database structure?

@julian said in Update from v0.7.0 to v1.4.0:

Use ./nodebb upgrade

'.' is not recognized as an internal or external command,
operable program or batch file.

But when i uninstall lwip and mmagic and then node app.js --upgrade on v 0.8.2

Error in mongodb module: Error: Cannot find module 'lwip'

I get errors not from NodeBB itself, errors gets from old and new environments dissonance. Especially from node_modules dependensies which in 0.7.0 times was like ~1.x.x in external libraries exept strictly =1.1.1.

I usualy can`t pick up environment for 0.7.0 on my home workspace. Forum live for 1.5 year on Heroku.
And I am not sure that nothing breaks if I start updatings on production.

I try to put the dump of base under version 1.4.0. But it`s breaks on creation index key_1_value-1 with dups. I clean up all dups with pair (_key, value), but catch another error from some lib.

Is there any fixed env for direct versions or maybe docker containers?

Hi. Sorry for my English.

I have forum on version 0.7.0 of NodeBB + MongoDB. I try to update step by step to 1.4.0 throught the version 0.8.0 and over and I stack in this step. I tried many versions of nodejs 0.12.x, 4.x, 6.x. Try to do it on Linux and on Windows. But in any case I faced with errors. It`s npm install errors with lwip or else, or errors with strict mode in modules when i try to update base and etc.

If I was try to update on 0.9.0 it is warn that I skip middle updates.

Is there any posible to update base manualy or else from 0.7.0 to edge version? Or maybe it posible install clear version and make import from old forum all users, categories and threads?

Thanks.

@hek said:

Did you by chance have dashes ("-") in the title?

No.

Hi guys.
Just happened unpleasant thing. Topic in which I wrote the message disappeared. I.e. it is not displayed in the last message and its category. Thus for a direct link I can enter it and write a message. And the notifications come if write in this topic something.

NodeBB 0.7.0

Hi guys!

I have previous 0.5.0-2 version of forum on Heroku. It works fine. When I updated NodeBB to 0.6.1 version it crashed with error. Any ideas?

2015-04-30T06:31:05.151177+00:00 heroku[web.1]: State changed from crashed to starting
2015-04-30T06:31:12.946261+00:00 heroku[web.1]: Starting process with command npm start
2015-04-30T06:31:16.159469+00:00 app[web.1]: Detected 512 MB available memory, 512 MB limit per process (WEB_MEMORY)
2015-04-30T06:31:16.159494+00:00 app[web.1]: Recommending WEB_CONCURRENCY=1
2015-04-30T06:31:16.817884+00:00 app[web.1]:
2015-04-30T06:31:16.817890+00:00 app[web.1]: > [email protected] start /app
2015-04-30T06:31:16.817892+00:00 app[web.1]: > ./nodebb start
2015-04-30T06:31:16.817893+00:00 app[web.1]:
2015-04-30T06:31:16.854535+00:00 app[web.1]: sh: 1: ./nodebb: Permission denied
2015-04-30T06:31:16.873738+00:00 app[web.1]: npm ERR! Linux 3.13.0-49-generic
2015-04-30T06:31:16.878037+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2015-04-30T06:31:16.878041+00:00 app[web.1]: npm ERR! [email protected] start: ./nodebb start
2015-04-30T06:31:16.878043+00:00 app[web.1]: npm ERR! Exit status 126
2015-04-30T06:31:16.878044+00:00 app[web.1]: npm ERR!
2015-04-30T06:31:16.878046+00:00 app[web.1]: npm ERR! Failed at the [email protected] start script './nodebb start'.
2015-04-30T06:31:16.878048+00:00 app[web.1]: npm ERR! This is most likely a problem with the nodebb package,
2015-04-30T06:31:16.878049+00:00 app[web.1]: npm ERR! not with npm itself.
2015-04-30T06:31:16.878050+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2015-04-30T06:31:16.878052+00:00 app[web.1]: npm ERR! ./nodebb start
2015-04-30T06:31:16.878054+00:00 app[web.1]: npm ERR! You can get their info via:
2015-04-30T06:31:16.878693+00:00 app[web.1]: npm ERR! npm owner ls nodebb
2015-04-30T06:31:16.878696+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2015-04-30T06:31:16.889120+00:00 app[web.1]:
2015-04-30T06:31:16.899848+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2015-04-30T06:31:16.866363+00:00 app[web.1]:
2015-04-30T06:31:16.874577+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2015-04-30T06:31:16.875101+00:00 app[web.1]: npm ERR! node v0.12.2
2015-04-30T06:31:16.876089+00:00 app[web.1]: npm ERR! npm v2.7.4
2015-04-30T06:31:16.897668+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2015-04-30T06:31:17.925842+00:00 heroku[web.1]: Process exited with status 1
2015-04-30T06:31:17.938969+00:00 heroku[web.1]: State changed from starting to crashed