Any way to deploy without running setup?

butteredroll

Hi everyone,

I'm trying to deploy to multiple nodes to go behind a load balancer.

the plan is also to have NGINX on each node to proxy NodeBB.

I have 2 questions.

Is there a way to manually install NodeBB? Like, do a test install, dump the DB, then restore it? Is there a way to manually install the dependencies and avoid the setup routine?
For the NGINX, I'm assuming the site name in the proxy config should be the IP address that NGINX is listening on, and not the URL pointed at the LB? BUT the NodeBB config should have the URL as whats pointed at the LB?

Thanks for any help on this and if anyone has a multi node setup and can lend some advice here, it would be GREATLY appreciated.

PitaJ

So essentially what setup does is run you through creating config.json, generates package.json, and sets up the database.

So after running setup once, you can just copy those around between everything else, adjusting the address of the database and whatnot, and running npm install to install the deps, or just copying the node_modules directory for that.

Also you'll probably want to set a custom uploads folder.

Nginx site name should be whatever your load balancer is passing through, which should usually be your site address. If you're using a load balancer already, though, you probably don't need nginx in between. the nodebb url should be the URL that you see in your browser when you visit the forum. (for instance, it's set to https://community.nodebb.org here)

butteredroll

@PitaJ thank you so much, this helps a lot.

butteredroll

@PitaJ said in Any way to deploy without running setup?:

So essentially what setup does is run you through creating config.json, generates package.json, and sets up the database.

So after running setup once, you can just copy those around between everything else, adjusting the address of the database and whatnot, and running npm install to install the deps, or just copying the node_modules directory for that.

Also you'll probably want to set a custom uploads folder.

Nginx site name should be whatever your load balancer is passing through, which should usually be your site address. If you're using a load balancer already, though, you probably don't need nginx in between. the nodebb url should be the URL that you see in your browser when you visit the forum. (for instance, it's set to https://community.nodebb.org here)

I was thinking nginx could be used to serve the static resources so that's why id put it there. But maybe youre right. The other issue is afaik, DO's load balancers dont support websockets so id need to upgrade them.

PitaJ

@butteredroll yes serving static assets is a good point. It is much more efficient with nginx.

butteredroll

@PitaJ said in Any way to deploy without running setup?:

@butteredroll yes serving static assets is a good point. It is much more efficient with nginx.

So one weird thing, it doest seem to create the build/public directory structure if I copy the package and config sons and run nom install in the node directory.

Any idea what's going on here? Is there a part of the setup that does this?

butteredroll

@PitaJ figured it out, I need to run nodes build