config.relative_path isn't set

DrRelling

I've just set up a NodeBB installation, and originally I just put my site's base URL (https://drrelling.dev) as the URL during installation. I'm hosting it on nginx on a subfolder via proxy_pass, however, so I've updated the url property in config.json to https://drrelling.dev/forum. The page loads on /forum, but all the asset files are still referring to the base URL and so are trying use https://drrelling.dev/assets/ as the assets folder. Opening one in a new tab and manually editing the url to be https://drrelling.dev/forum/assets/ shows the expected file.

Poking around in the code I found the config.relative_path attribute, and sure enough when I checked the config in the browser it was set to "". Is NodeBB having trouble parsing my weird URL, or is there something else I'm doing wrong?

Thanks!

<baris>

When you make a change to config.json you need to restart nodebb for it pickup those changes.

DrRelling

I'm running ./nodebb build after the changes. Would that do it?

DrRelling

Nope, a build isn't sufficient - it needs a restart too. Thanks for this! It's up and running now

DrRelling

Would it be possible to add a line calling that out explicitly in https://docs.nodebb.org/configuring/config to make it obvious to stupid people like me?