@julian I assumed that since this was a managed container environment where containers are ephemeral and can be moved around, I would need to run ./nodebb setup every time. Is my assumption wrong? Can I just run setup once to populate the database and then just run ./nodebb build the other times?

Your config.json should look like this for multiple ports { "url": "http://example.org", "secret": "your-secret-goes-here", "database": "mongo", "port": [4567, 4568, 4569], "mongo": { "host": "127.0.0.1", "port": "27017", "database": "0" }, "redis": { "host":"127.0.0.1", "port":"6379", "database": 0 } } After ./nodebb setup modify config.json remove port from url and add the port array. Then use ./nodebb start to start nodebb. It should start up 3 nodejs processes, you can check if it worked with top