Pointing Domain To NodeBB Forum (Digital Ocean)

Technical Support
  • Hello,

    I'm ready to launch my NodeBB forum to the public. I've registered my domain on GoDaddy, and I know I need to point that domain to my Digital Ocean droplet IP address.

    At least, I believe that's how it works. I've looked over some other discussions on this and seem to get a bit lost. For example, do I need to change my config.json base url to http://domain.com, and then use ngix as well? Or, can this all be done through Digital Ocean and Godaddy?

    Steps I've taken so far:

    In Digital Ocean, under the DNS tab:

    I've added my GoDaddy domain to my droplet and it filled the IP address automatically (my droplet Server IP).

    *In GoDaddy: *

    Under DNS Zone file, I changed my A(Host) to point to my droplet server IP address (I don't know if that was a step in the right direction, or if I should have left it as it was).
    Considering my puzzle pieces are these listed below. (It's easier for me to think of them as parameters to plug in somewhere):

    • Droplet Server IP

    • DNS A(Host)

    • config.json

    • ngix

    • GoDaddy Domain*

    I believe I have all the pieces, I just need some assistance on putting them all together. I've never done this before, so any help on this would be very appreciated. I hope I was clear my my explanation, and thank you in advance.

    Edit: In addition, is there a way to run the Redis Server on Digital Ocean forever, without having to go into my terminal/console and starting it using ./nodebb start?

  • Thank you very much, that did the trick. However, will this allow my Redis server to always run? If not how can I configure that?

  • You can check redis.conf file for daemonize no option and change it to yes.

  • @JonDoe12 Redis should be running automatically on start if you installed it using apt

  • Yes, but I don't want to manually start it everytime. I want it to run forever, even when I end my ssh sessions, when I'm not around, etc. Does it already do that? I could be mistaken.

  • Yes, it will work in the background.

Suggested Topics

  • 1 Votes
    6 Posts

    @Rektalizer Evidently you have a mish mash of "names" here:

    irrisuite.ru - as noted above, this one resolves to IP address

    www.irrisuite.ru -- this one also resolves to IP address

    forum.irrisuite.ru -- this one resolves to ... same as before.

    Which are you actually using? If you intend to use more than one of the above then which will be your nodebb forums URL?

    Or is it your intention to have ALL of the above point to your nodebb forums? Note that this can create issues on down the road if, for e.g., you decide to "spin off" www for e.g. a blog or other purposes.

    As for your nginx logs immediately up post, have you adjusted your nginx server_name config to jive with your nodebb config.json yet?

  • 0 Votes
    7 Posts

    @Thadeusz-Lay coz they may not want to use your theme. Making it a plugin will enable anyone to use it with any theme. If you want to keep things simple and don't want to publish your theme with custom fields, then you can add the fields in the theme.

  • 0 Votes
    1 Posts

    Hihi, i'm going to migrate the Ghost-Blog's topics to my new Nodebb site, there are dozens of topics, and i use the nodebb-plugin-blog-comments to move the topic to the Nodebb site, and my question is : How to map the old Ghost-Blog topic's url to the new Nodebb topic's route ?

    For example:

    There is a topic in Old Ghost-Blog: http://mysite.com/2016/06/23/guipin-jia/ And i migrated above topic to the new Nodebb: http://mysite.com/topic/12/guipin-jia/

    I wish that the nodebb can redirect the old Ghost-Blog's topics url to the new nodebb's topics url, when the users browser the old Ghost-Blog's urls~

    Please help, many many thanks~ @julian @psychobunny @baris @pichalite

  • 0 Votes
    5 Posts

    @JCSP16 are you sure you hit the save button afterwards?

  • 1 Votes
    1 Posts

    Hi guys!

    I have previous 0.5.0-2 version of forum on Heroku. It works fine. When I updated NodeBB to 0.6.1 version it crashed with error. Any ideas?

    2015-04-30T06:31:05.151177+00:00 heroku[web.1]: State changed from crashed to starting
    2015-04-30T06:31:12.946261+00:00 heroku[web.1]: Starting process with command npm start
    2015-04-30T06:31:16.159469+00:00 app[web.1]: Detected 512 MB available memory, 512 MB limit per process (WEB_MEMORY)
    2015-04-30T06:31:16.159494+00:00 app[web.1]: Recommending WEB_CONCURRENCY=1
    2015-04-30T06:31:16.817884+00:00 app[web.1]:
    2015-04-30T06:31:16.817890+00:00 app[web.1]: > [email protected] start /app
    2015-04-30T06:31:16.817892+00:00 app[web.1]: > ./nodebb start
    2015-04-30T06:31:16.817893+00:00 app[web.1]:
    2015-04-30T06:31:16.854535+00:00 app[web.1]: sh: 1: ./nodebb: Permission denied
    2015-04-30T06:31:16.873738+00:00 app[web.1]: npm ERR! Linux 3.13.0-49-generic
    2015-04-30T06:31:16.878037+00:00 app[web.1]: npm ERR! code ELIFECYCLE
    2015-04-30T06:31:16.878041+00:00 app[web.1]: npm ERR! [email protected] start: ./nodebb start
    2015-04-30T06:31:16.878043+00:00 app[web.1]: npm ERR! Exit status 126
    2015-04-30T06:31:16.878044+00:00 app[web.1]: npm ERR!
    2015-04-30T06:31:16.878046+00:00 app[web.1]: npm ERR! Failed at the [email protected] start script './nodebb start'.
    2015-04-30T06:31:16.878048+00:00 app[web.1]: npm ERR! This is most likely a problem with the nodebb package,
    2015-04-30T06:31:16.878049+00:00 app[web.1]: npm ERR! not with npm itself.
    2015-04-30T06:31:16.878050+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
    2015-04-30T06:31:16.878052+00:00 app[web.1]: npm ERR! ./nodebb start
    2015-04-30T06:31:16.878054+00:00 app[web.1]: npm ERR! You can get their info via:
    2015-04-30T06:31:16.878693+00:00 app[web.1]: npm ERR! npm owner ls nodebb
    2015-04-30T06:31:16.878696+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
    2015-04-30T06:31:16.889120+00:00 app[web.1]:
    2015-04-30T06:31:16.899848+00:00 app[web.1]: npm ERR! /app/npm-debug.log
    2015-04-30T06:31:16.866363+00:00 app[web.1]:
    2015-04-30T06:31:16.874577+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
    2015-04-30T06:31:16.875101+00:00 app[web.1]: npm ERR! node v0.12.2
    2015-04-30T06:31:16.876089+00:00 app[web.1]: npm ERR! npm v2.7.4
    2015-04-30T06:31:16.897668+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
    2015-04-30T06:31:17.925842+00:00 heroku[web.1]: Process exited with status 1
    2015-04-30T06:31:17.938969+00:00 heroku[web.1]: State changed from starting to crashed