never mind been a while since i installed nodedbb, that prompt was for database = redis not the redis db number which came later on 🙂./nodebb setup 1/8 09:58  - info: NodeBB Setup Triggered via Command Line Welcome to NodeBB! This looks like a new installation, so you'll have to answer a few questions about your environment before we can proceed. Press enter to accept the default setting (shown in brackets). URL used to access this NodeBB (http://localhost:4567) Please enter a NodeBB secret (09df113d-0255-48b7-8e21-c2d0eba3be54) Which database to use (redis) 1/8 09:58  - info: Now configuring redis database: Host IP or address of your Redis instance (127.0.0.1) Host port of your Redis instance (6379) Password of your Redis database Which database to use (0..n) (0) 3 Configuration Saved OK firstname.lastname@example.org node_modules/redis email@example.com node_modules/connect-redis └── firstname.lastname@example.org (email@example.com) Populating database with default configs, if not already set... Enabling default theme: Persona No categories found, populating instance with default categories 1/8 09:59  - warn: No administrators have been detected, running initial user setup
NodeBB Configurations Migration
I'm seeking advise on the most reliant and efficient way to migrate a NodeBB instance's settings/configurations to another NodeBB instance. I have tried to look into the mongodb "Config" document but it doesn't contain all the configurations that have been set. For example, the Navigation settings are stored separately in its own documents.
Also need to migrate the plugins settings too but i can't seem to find them on mongodb documents. If anybody has done something similar kindly please share your knowledge.
The purpose of this task is to allow replication of an exact setup of NodeBB to another new instance for testing.
Giggiux last edited by
@yapne In order to do testing, what I would do is to clone mongodb, then configure nodebb-test to connect to the cloned one and work on that
@giggiux I want to store the configuration/settings into SCM so that in the worst case scenario we can rebuild the instance. And i don't want to clone the datasets either