@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

Hi,

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.

Many thanks

Nelson

@yariplus the database is hosted on Mongo Atlas. why would you say it is the database?

@pitaj I believe Bluemix Cloud Foundry is using round robin algorithm.

I did modify the webserver.js file in order for Cloud Foundry to inject the internal port. Below are the changes and i'm starting NodeBB using node app.js

var port = process.env.PORT;
var socketPath = isSocket ? process.env.PORT : '';

the URL in config,json, i think it is the reverse PROXY url given by Bluemix CF. Also the port in config.json i have also left it as 4567. Not sure if this correct in my case though.

I'm facing the same issue when i deployed onto IBM Bluemix Cloud Foundry. On a single instance NodeBB works fine but after scaling it repeatedly getting the error message state above. No idea how to resolve this. I suspect it has something to do with the URL in config.json that is not compatible with the LB ... it is a shame though.

Wondering if it is the same on Digital Ocean when scaled up? @PitaJ Are you able to comment please?

Thanks

@PitaJ bumping up

@pitaj There is a specific reason why I am not using group. Nodebb doesn't have the capability to assign user's privileges at the topic level. Hence, we are using category as a work around for this missing feature.

Externally to NodeBB, we are giving end users the functionality to create category dynamically and assign users to it. By using group, it may end up creating a lot of groups that are going to be nightmare to maintain. Therefore, i am planning to assign the users directly to the category instead. I think the API does not support this requirement just yet. If you can advise if there is another better way to do this please? Or possibly to enhance the API to assign user's privileges to the category?

Many thanks

Nelson

@yapne said in Assign Group to Category via Write API:

@baris @julianlam How do i add user(s) to the category via this write API? Are you able to advise please? Thanks

Doesn't seem the API support this. Are you able to confirm please?

@baris @julianlam

@baris @julianlam How do i add user(s) to the category via this write API? Are you able to advise please? Thanks

@pitaj thank you. Will give it a try.