Take a look at this article: http://nginx.org/en/docs/http/server_names.html#miscellaneous_names
Adding a new server block with your IP address in the server_name field should catch those...:
server {
listen 80;
listen 4567;
server_name 123.456.789.101;
return 301 http://lukesawesomeforum.com;
}
I apologise in advance for my most likely not working nginx code
@zenkamal ha, thanks, only one or two small issues I had to worry about, nothing too major.
I got to the point where I could either wait a bit longer, or just get the transfer done, so I voted just do it and deal with any issues after.
@lukelarris What you propose is definitely possible. We just haven't tried it.
Notes
In app.js, we listen for a passed-in argument called config
By default, it looks for a config.json present in the root directory
If you ran NodeBB with ./nodebb start --config="/relative/or/absolute/path/to/another/config", it should correctly start NodeBB using the second config file.
I don't know what would happen if you pointed --config to a non-existant file -- would NodeBB run through the setup script and save the new config? Beats me.
Let me know how you get on!
