Thanks @julian

I managed to solve this. For brand new users who aren't too familiar with web servers and backend (like me) it was fairly easy after some research. Hopefully this will save time for anyone in the future looking to do the same thing.

How to redirect subdomain to NodeBB IP w/ Nginx

This assumes that you have already added an A Record that points your subdomain to the NodeBB IP. This is fairly easy to use from your hosting provider.

There are many tutorials out there and they were helpful but, to me it felt there was plenty of information scattered all over.

This is what I did to get my subdomain to redirect to my NodeBB installation on DigitalOcean.

/* Update your package list to get the latest versions and Install Nginx*/
sudo apt-get update
sudo apt-get install nginx

/* Nginx is located in /etc/nginx by default */

cd /etc/nginx

/* You want to go to your list of available sites here */
cd sites-available 

/* Create a copy of the default config and name it to your sites name */
cp default <your website name>

/* Add configuration files for your website  */
nano <your website name>

/* Copy and paste config found here: https://docs.nodebb.org/en/latest/configuring/proxies/nginx.html 
 into the server section of the code. 
 NodeBB runs on port <your IP here>:4567 by default  */

/* Enable it */
cd sites-enabled
ln -s ../sites-available/<your website name>

/* Restart nginx */
sudo service nginx restart

Go to your subdomain and make sure it works. Also be sure to change your config.json to your new url.

Hopefully this helps some beginners out there!

If anyone is a badminton fan, I have created a new community for all badminton enthusiasts.

You can check it out at Badminton Birdie Forums

Let me know what you guys think!!

I want to create a snapshot of my droplet on digital ocean but, in order to do that I have to power off my droplet.

At first, I thought redis saved my dump.rdb file automatically but, I turned it off without doing anything in the redis command line.

This caused me to lose some of my settings that I had previously installed and had to re-work it all again.

Do I just run bgsave in redis-cli and then turn off the droplet to create my snapshot?

Don't want to risk losing all of my data again before powering it off.

I am using an Ubuntu server on the $5 tier offered by D.O.

@codejet User registration should be opened. The registration type is set to normal, so pretty sure it's not invite only at this point
World championships are coming soon, hope to attract some users then too!

Thanks @baris that did the trick

@julian I think I managed to solve this problem, not 100% though

I changed the permission to 755 for my working root directory and the dump.rdb permissions to 644. I also changed the ownership of my working root directory to redis as well.

Upon running redis-cli bgsave and then checking the redis-server.log I am greeted with this:

933:M 10 Jul 12:52:17.908 * Background saving started by pid 20754
20754:C 10 Jul 12:52:17.917 * DB saved on disk
20754:C 10 Jul 12:52:17.918 * RDB: 0 MB of memory used by copy-on-write
933:M 10 Jul 12:52:17.946 * Background saving terminated with success

It says 0MB of memory used by copy-on-write? Does this mean it saved?

@PitaJ Thank you!

I followed the steps and after v1.4.0 when I checked back into v1.x.x and ran ./nodebb upgrade I received this error now:

error: Build failed: Unexpected character ''

It seems i only get this on v1.4.4 I reverted back to v1.4.3 and it seems to be fine for now

I am finally able to upgrade an existing project to the latest version of NodeBB however, upon doing so I receive

error: [upgrade] NodeBB upgrade could not complete, as your database schema is too far out of date.
error: [upgrade]   Please ensure that you did not skip any minor version upgrades.
error: [upgrade]   (e.g. v0.1.x directly to v0.3.x)

I expected something like this after not upgrading in forever.

Are there any way of getting up to date? Or am I stuck on v0.9.x? How would I revert back to it?

Thanks!

I'm currently on v0.9.4 and want to update to the latest version (v1.0.4-auto.2 as of this writing)

I'm looking at the docs and it says to use

$ git fetch    # Grab the latest code from the NodeBB Repository
$ git checkout v0.4.x    # Type this as-is! Not v0.4.2 or v0.4.3, but "v0.4.x"!
$ git merge origin/v0.4.x

To go to v1.0.4 would I just replace 0.4.x with v1.0.x? Do I need to prefix any auto-.x as well? I've had bad experiences updating in the past and don't want to mess up the forum right now!

Try npm install ip then upgrade again

I asked a general question to upgrading from a minor branch here a while back: Re: Newbie Upgrade Question From v0.9.0

I am currently on v0.9.4 and was wondering do I need to do anything before hand to upgrade to the latest version of 1.x.x? I noticed v1.0.1 is the latest version as of this writing.

I always seem to have some form of problem whenever I upgrade to a newer version of NodeBB and just want to relieve myself of any worries before I attempt the upgrade.

@qgp9 I am using the same config as you and I'm on v0.9.4 of NodeBB. The email is still not being sent through... Am I missing anything else? (I'm using the test email option that @julianlam suggested)

Edit: I received it after a few minutes of typing this!

Hmm, I've tried using the sandbox domain and it does not seem to be sending any emails. I am simply validating an existing users email again (or is there a better way to generate an email?)

I signed up for Mailgun now that Mandrill is out of the picture.

I am having some troubles configuring the settings however. I have pasted the API key that is provided but, I did not set up my own domain (it gives me the optional option). Do I need to fill in both the API and Domain Name fields inside the NodeBB Mailgun settings? I figured that the API key would automatically link to my forums in the NodeBB ACP is this how it works?

If not, Mailgun gave me a default domain name (something like sandboxbe3b289fa5ac47328cb782919b581a11.mailgun.org ) would I just paste that in there? I am not too sure how to switch over to Mailgun from Mandrill.

If we are on v0.9.4 do we just simply follow the docs to upgrade? When updating from v0.9.0 to v0.9.4 I had a few dependencies that were missing and that caused some headaches in the upgrade process. Will this be a seamless upgrade?

Thanks for the info everyone I will take a look at all the recommendations. Just a pain to set everything up again on a new service.