A little help with NodeBB on Docker?

Technical Support
  • So I'm VERY new to Docker.com and stuff. I've noticed that I could get Ubuntu, or Nginx or many other things on a docker.

    I just want to set up a Forum on Docker. The tutorial given is kinda outdated. Can anyone tell me what I should do?

    My questions: Please answer all

    1. Which software thing do I take? Nginx? Ubuntu? What?! I heard NGinx is widely used.
    2. Based on which software I should take, could you tell me what steps I should follow? Any tutorial link is appreciated.
    3. By taking that software, what are the flaws? Like data will reset, it will go offline quickly? Etc.
    4. Does docker have any disadvantages? Is it 24/7? Do I need to pay? Anything? I'm new to it.

    Please help me. I'm doing it for a friend. Thank you.

  • Anybody? 😞

    1. I use Nginx and Mongodb!
    2. I use docker and it works great 🙂
  • @Jenkler said in A little help with NodeBB on Docker?:

    1. I use Nginx and Mongodb!
    2. I use docker and it works great 🙂

    Umm could you tell me if you know any tutorial on how to use Mongodb and nginx?

    1. Use nginx as the reverse proxy, it will give you better performance serving static assets.
    2. Use ubuntu, there's more support for it
    3. Use MongoDB, it's better on memory usage at the sacrifice of speed (hardly noticeable)
    4. there will always be technical difficulties, be prepared to deal with them
    5. Look at some tutorials on how to properly secure your instance, i.e. using ssh keys, strong passwords, not exposing DB ports to the world, etc
    6. I wouldn't use docker for nodebb just yet, it's not well supported, last I checked.
    7. you only need to pay as much as you're willing to. I hear Openshift is free (if you don't count the time you spend setting things up)
    8. Is Docker 24/7? I'm not sure what you mean by that.

    It sounds like you've done some very light, basic research. Keep reading 🙂

  • @Bri said in A little help with NodeBB on Docker?:

    1. Use nginx as the reverse proxy, it will give you better performance serving static assets.
    2. Use ubuntu, there's more support for it
    3. Use MongoDB, it's better on memory usage at the sacrifice of speed (hardly noticeable)
    4. there will always be technical difficulties, be prepared to deal with them
    5. Look at some tutorials on how to properly secure your instance, i.e. using ssh keys, strong passwords, not exposing DB ports to the world, etc
    6. I wouldn't use docker for nodebb just yet, it's not well supported, last I checked.
    7. you only need to pay as much as you're willing to. I hear Openshift is free (if you don't count the time you spend setting things up)
    8. Is Docker 24/7? I'm not sure what you mean by that.

    It sounds like you've done some very light, basic research. Keep reading 🙂

    Thank you so very much. I'm pretty much a noob. And for nginx and stuff, do i install it on my PC? Or online somehow? Cause I want it to be hosted somehow, where I don't need to keep my laptop running 24/7 or anything like that. Thank you sooooo much tho

  • Everything would be installed on a VPS (or, virtual private server). Think of it as a computer somewhere that stays on forever (well, 99.99% of the time), that you log into remotely (ssh) and install there. If you're not already, you'll have to get used to using some command line stuff.

    You can start here:
    https://www.digitalocean.com/community/tutorials/how-to-create-your-first-digitalocean-droplet-virtual-server

  • @Bri said in A little help with NodeBB on Docker?:

    Everything would be installed on a VPS (or, virtual private server). Think of it as a computer somewhere that stays on forever (well, 99.99% of the time), that you log into remotely (ssh) and install there. If you're not already, you'll have to get used to using some command line stuff.

    You can start here:
    https://www.digitalocean.com/community/tutorials/how-to-create-your-first-digitalocean-droplet-virtual-server

    Digitalocean is paid though, isn't it? 😕 I'm cheap. Lol. Free only. XD. Sorry. 😞

  • @Bri would Microsoft Azure work?

  • @Bri said in A little help with NodeBB on Docker?:

    Look at some tutorials on how to properly secure your instance, i.e. using ssh keys, strong passwords, not exposing DB ports to the world, etc

    This is something I really want to stress. This part of setting anything up on the internet is overlooked way too often, and what we get is a bunch of botnets we have to defend against in DDoS attacks.

    Things like:

    • disable root login
    • change the ssh port to something non standard
    • remove any bits you don't need, like postfix
    • test, and make sure you don't have ports open to the world that you don't intend (i.e. anything other than ssh, 80, and 443)
  • @Friendship Yes Azure would be fine. Free is ok too, I've run stuff off a laptop at my house and used a free subdomain for a long time (but now I make money so I can pay to not have to deal with things like the IP changing or someone turning off the computer)

    The tutorial is still valid BTW, just apply some of the stuff to what you're going to do on some other provider. DO actually has a lot of good tutorials for this stuff.

  • @Bri said in A little help with NodeBB on Docker?:

    @Friendship Yes Azure would be fine. Free is ok too, I've run stuff off a laptop at my house and used a free subdomain for a long time (but now I make money so I can pay to not have to deal with things like the IP changing or someone turning off the computer)

    The tutorial is still valid BTW, just apply some of the stuff to what you're going to do on some other provider. DO actually has a lot of good tutorials for this stuff.

    Thank you @Bri alot. You've helped me a lot today. 🙂 I thank you a lot. I'll go with Azure. Try using Tutorials here and there if I ever get confused, I'll just ask over here. Because I know for sure, NodeBB users are helpful 🙂

    Thank you.

  • Lots of people here willing to help, just have to show your effort 🙂


Suggested Topics


  • 1 Votes
    4 Posts
    236 Views

    Looking at those numbers, definitely.

    We typically opt for a horizontally scaled solution the moment we see the "concurrent users" metric hit 100. This is a conservative estimate, NodeBB can easily handle more, as you've experienced, but it is a good point to start thinking about solutions.

  • 0 Votes
    7 Posts
    1k Views

    @pitaj

    No sorry, that didn't solve. But following worked:

    After importing mybb, upgrade it to v1.16.0 which produces "Error: ENOENT: no such file or directory, open '/nodebb/node_modules/nodebb-plugin-require/plugin.json' " as mentioned above. Back up both database and any image files imported from mybb under public/uploads/files Delete whole nodebb files and database Install original v1.16.0 (git clone -b v1.16.x https://github.com/NodeBB/NodeBB.git) Remove only the database, then restore database and image files using backups Works well, it doesn't produce any error even after installing quickstart plugin.

    Additionally, https://github.com/NodeBB/nodebb-plugin-quickstart doesn't work on v1.16.0.
    It shows following error on Chrome and the page got frozen while loading:
    colorpicker.js:11 Uncaught TypeError: n.ColorPicker is not a function
    at HTMLInputElement.<anonymous> (colorpicker.js:11)
    at Function.each (jquery.js:381)
    at C.fn.init.each (jquery.js:203)
    at Object.n.enable (colorpicker.js:8)
    at o (admin.js:31)
    at Object.i.init (admin.js:9)
    at ajaxify.js:336
    at Object.execCb (require.js:1696)
    at n.check (require.js:883)
    at n.<anonymous> (require.js:1139)

    Anyways, it's not to be discussed here I guess.
    Thank you very much!

  • 0 Votes
    3 Posts
    360 Views

    @scottalanmiller Same as given on NodeBB Doc

  • 0 Votes
    3 Posts
    1k Views

    I've found the cause, the Wordpress SSO plugin was causing issues.

  • 0 Votes
    3 Posts
    2k Views

    @pitaj

    Got it figured out. Basically, you have to form a "redirect chain" kinda. I think I was creating an infinite loop of redirection or excluding a specific case (www. for 443 and for 80 separately) in my above nginx config. I ended up having to redirect 80 http://www.domain.com, 80 http://domain.com AND 443 https://www.domain.com all to 443 https://domain.com and then that third block is where all the master logic for the activity goes, if that makes sense.

    In my original post, I was combining too many of these cases into just 2 blocks. In addition, I also added location / {} and wrapped that around my return 301 statements.

    This fixed the problem entirely with both the domain and the forum malfunctioning. Last but not least, I wanted to mention that I also added proxy_set_header X-Forwarded-Proto $scheme; to the main logic block near the other proxy_set settings, which fixed a csrf error as well. So we're all good now!

    Very exciting stuff. I appreciate the quick replies and help. Happy to use NodeBB for my new site!