NodeBB's periodic releases are located in the Releases. These releases contain what is usually considered the most bug-free code, and is designed to be used on production-level instances of NodeBB.
You can utilise git to install a specific version of NodeBB, and upgrade periodically as new releases are made.
To obtain the latest fixes and features, you can also
git clone the
latest version directly from the repository (
master branch), although
its stability cannot be guaranteed. Core developers will attempt to
ensure that every commit results in a working client, even if individual
features may not be 100% complete.
As always, the NodeBB team is not responsible for any misadventures, loss of data, data corruption, or any other bad things that may arise due to a botched upgrade - so please don't forget to back up before beginning!
NodeBB's upgrade path is designed so that upgrading between versions is straightforward.
1. Shut down your forum
While it is possible to upgrade NodeBB while it is running, it is definitely not recommended, particularly if it is an active forum:
$ cd /path/to/nodebb $ ./nodebb stop
2. Back up your data
Backing up Redis
As with all upgrades, the first step is to back up your data! Nobody likes database corruption/misplacement.
All of the textual data stored in NodeBB is found in a
.rdb file. On
typical installs of Redis, the main database is found at
Store this file somewhere safe.
Backing up MongoDB
To run a backup of your complete MongoDB you can simply run
which will create a directory structure that can be restored with the mongorestore command.
It is recommended that you first shut down your database. On Debian / Ubuntu it's likely to be: sudo service mongodb stop
Store this file somewhere safe.
Uploaded images and files are stored in /public/uploads. Feel free to back up this folder too:
cd /path/to/nodebb/public tar -czf ~/nodebb_assets.tar.gz ./uploads
3. Grab the latest and greatest code
Navigate to your NodeBB:
$ cd /path/to/nodebb.
If you are upgrading from a lower branch to a higher branch, switch branches as necessary. Make sure you are completely up-to-date on your current branch!.
For example, if upgrading from
$ git fetch # Grab the latest code from the NodeBB Repository $ git checkout v1.12.x # Type this as-is! Not v1.12.0 but "v1.12.x"! $ git merge origin/v1.12.x
If not upgrading between branches (e.g.
v1.12.1, just run
the following commands:
$ git fetch $ git reset --hard origin/v1.12.x # Replace v1.12.x with the branch name!
This should retrieve the latest (and greatest) version of NodeBB from the repository.
Don't know what branch you are on? Execute
git rev-parse --abbrev-ref HEAD to find out.
Alternatively, download and extract the latest versioned copy of the code from the Releases Page. Overwrite any files as necessary. This method is not supported.
4. Run the NodeBB upgrade script
This script will install any missing dependencies, upgrade any plugins or themes (if an upgrade is available), and migrate the database if necessary.
$ ./nodebb upgrade
./nodebb upgrade is only available after v0.3.0. If you are
running an earlier version, run these instead:
ls -d node_modules/nodebb* | xargs -n1 basename | xargs npm update
node app --upgrade
5. Start up NodeBB & Test!
You should now be running the latest version of NodeBB.