@gotwf 9.5 (Ya I know is a very old version 😑 )

@pitaj it worked.

In your setup redis will be used for sessions, pubsub and socket.io will use it to pass around messages.

Each nodejs process has it's own post cache, you can see the caches at /admin/advanced/cache.

Redis pubsub is also used to clear cache on the other nodejs process when it is cleared on one nodejs process. For example when a post is edited it's cache will be cleared on the other nodes.

@PitaJ said in Any tips for installing NodeBB on AWS Lightsail?:

As long as Lightsail doesn't limit the capabilities of their VPS, I don't see why it would be any different from a normal install on Ubuntu.

yeah, it's identical. LightSail ends up being exactly like a DO or Vultr.

Thank you for the explanation. I will probably use a third-party database (firebase) for payments.
Using firebase, different operations can be done on the client side, without disturbing the main server. I think this is very useful for a smoother user experience.

Hello, I'm hosting my NodeBB on Digital Ocean and I want to move everything to an other database. We use MongoDB and we have a few problems. We don't know the MongoDB admin password/username.

Do you know a way to do this or is there a plugin that makes this easier to do?
Any help/advice is welcome and are there things we should do and don't do?

I'm looking to use Azure CosmosDB mongoDB API with more than 10GB, so I need a shard key to get unlimited storage. Is there anything I have to do with NodeBB for the shard key?

Also, I couldn't find this anywhere and have no forum experience, but excluding media, how much storage does a moderate forum take up?

@gotwf Thanks.

Sorry I was AWOL yesterday. I was in that Canton, TX tornado! Okay, not "in" it, but was in Canton when it happened.

@scottalanmiller So unfortunately none of the versions worked with our database any more. We even tried 1.11.2 and went back to 1.10.2 on mongodb 3.2 as well.

Now, we've updated mongodb to 3.4 and picked up an old database backup to migrate from 3.2 to 3.4 on the latest nodebb (1.11.2). Its working properly now.

However, a warning for people on older versions of mongodb when updating to 1.11.x onward.

MongoDB changes licensing creating cascade of open source requirements.

Take a look, if you are deploying NodeBB with MongoDB ever, or write any code for anything that touches it, be aware that you may be forced to open source anything and everything.

@SparaxVenator try running npm install

Does the forum logs give an error when it crashes?

Do you have mongo and nginx logs on?

There should be some useful information in one of the logs as to what is happening.

@alff0x1f excellent! Thank you very much for those printouts. Swap it is, then 😃

@pichalite Thanks 🙂 Rookie mistake by me

No they return the score of the value.

db.sortedSetScore(set, data.name, function(err, score) { console.log(score); });

NodeBB w/ MongoDB still works just fine even though the kerberos dependency doesn't build, it just means you can't connect to MongoDB servers utilising kerberos authentication.

Would prefer not to have to add libkrb5-dev to the list of dependencies, so investigating alternatives...

Well, damn. Didnt know that.

Okay, Thanks for your phenomenal help, @pichalite.

Gonna mess around with this proxying and nginx a bit now that everything is moving forward again.

I had back this problem a 2nd time 2 days ago, I don't know if it's related but I was doing iptables FW settings on the VM, I had nodeBB running, and also redis and from my computer desktop redis desktop manager connected to DB.
Then I made a mistake in iptables, blocked all redis port (even local), saying nodebb unable to connect to redis (so as redis desktop manager) then when I openned back 6379 port, all data was gone, not sure if it's related, just an information.

Thank you @markkus and @jarey for your replies. I did what you suggested about re-installation and the problem persisted. I then discovered something...

...the installation manual may be outdated. The file in question on Step 7 is mongod.conf instead of mongodb.conf.

Step 7 Corrected.png

step7.png

Can @psychobunny or whoever in charge of the Doc double check this and make the proper correction?

The structure looks not friendly at all.