@brophy Cool to see another MTA community here
am was a happy NodeBB user! (But I will certainly use it again!)
I am a full-time student Applied Mathematics, and Computer Science is one of my side-interests. I consider programming as a hobby.
In my study I'm focused at discrete mathematics: mainly algebra and optimization.
Posts made by JasperNL
RE: Nodebb Hosting - Fully Managed - Simple to use
ALL INSTANCES COME WITH A 10GBPS CONNECTION! This means that NO LAG is anywhere to be found. Your Nodebb install will load in seconds no matter who accesses it.
If you're using Vultr (as your IP suggests), then 10GBPS is only accessable from their bare metal instances, and not from their VPS instances. The 10GBPS is also "burst", so not guaranteed. Neither does the connection speed mean that it has "no lagg anywhere to be found" because of peering: especially asian customers (Japan, Singapore, India, Korea) cannot get close to 10 MBits when connecting to the US instances of Vultr, even if the instance has a 10GBPS port.
I also believe that you share your resources over all or a portion of your customers, because of the price. That may be worth mentioning as well, as it's an obvious deal-breaker for many customers.
RE: How to Load Balance for all CPU Cores
@pummelchen There is an issue in one of our dependency that effects mongodb, https://github.com/scttnlsn/mubsub/issues/61, in the meantime you can install redis and add a redis block in your config.json so pubsub uses redis instead of mongodb. That should get rid of the error you are seeing in the logs.
I had the same error. Adding redis as additional db did the trick. A question: if it's fixed, can i disable redis without a problem or should I flush changes to mongo somehow? (Memory is scarce, so I prefer to disable redis if possible)
RE: NodeBB - Full Stack Setup
I think this is a good tutorial, and will prove useful to many users! However, I have some remarks that I'll list below.
What has DNS to do with a stack? Not a lot, thats right, but as in my previous guide we will target the maximum possible performance. Therefore, we will also try to reduce the DNS resolving time.
To achieve this we will route our domain through CloudFlare. Just sign up and follow the instructions. Once done be sure to have DISABLED CloudFlare in the DNS settings (grey clouds).
But why? Due to the use of CloudFlare the server response time can be delayed around 0,7s, which is quite a lot, considering we want the maximum performance. Instead we will just make use of CloudFlare's fast DNS network.
Depending on the scale you want to deploy the server on, cloudflare can actually be a good idea. Especially if you're afraid of DDoS attacks. There are basically three "modes" that you can choose from
- The mode in which you do not use anything of cloudflare, which you suggest.
- The mode in which you use cloudflare to cache static assets, but route websockets through your own server. This can be achieved by setting the
config.json. This does not save you from DDoS attacks, as the origin server can be found quite easily. This is the mode that I would recommend.
- Use cloudflare as websocket proxy. This secures you from DDoS attacks and works fine. This mode has a lot of cons, because cloudflare can kill the websocket connections without any specific reason, and you have the cloudflare proxy delay that you're considering. I would recommend this for small-scale sites only.
Change it to a number like 1990 for example. Once edited hit
Ctrl+X. Confirm with
Auts. This is not secure. Besides the "security by obscurity" arguments that this insecure, there are also practical objections with this port. Any port >1024 can be hijacked by any user on the box, whereas ports <1024 are reserved for the system/root user. So if you want to change the port (because you may believe that it's actually secure), keep it <1024!
I always recommend to keep the SSH service at port 22 (as this is designed for it). For security, you can install fail2ban and set up a SSH keypair authentication instead of password authentication. Also: If your host gives you a root password, the first thing you should do is changing it!
Now lets get onto NodeBB. Instead of MongoDB, we will skip into the future and go with Redis. Super fast, super simple.
MongoDB has a future as well, and the benefits of redis over mongo.
Again, great tutorial!
RE: Who is using NodeBB?
Your automatic translation creates some style overflows when "topics" and "messages" are translated to somewhat large words That may be something to look at
RE: German translation (Du / Sie)
Many forum/blog software comes with two German language versions, formal and informal. As German is already quite well translated, maybe it's an idea to create a branch of the current one, and call it "German Informal". (or German Formal, depends on what's better)