So rezzing this thread for OBVIOUS REASONS.
I am feeling a bit anxious to put my money where my mouth is to help where I can. I am somewhat technically-inclined, but I am not a fully experienced server administrator, dev, coder, what have you. I can hesitantly and anxiously work my way through clear instructions, but I can tell you that trying to set up something like the Arxcode Evennia was a Trial for me (and then I never did quite get it working).
From going over this thread again, it sounds like the various proposed solutions (or attempted solutions) were:
- Stay on NodeBB and migrate the database from Redis to MongoDB. This would either require someone writing a custom migration solution or paying NodeBB to do it for us. When Ark mentioned this, he dropped a dollar tag of $500. (FWIW, I am assuming that was the cost for NodeBB's team doing it, but I could be wrong there.) This MIGHT fix the memory leak issue, but we don't actually no for sure. There may be something else about our setup causing issues.
- Stay on NodeBB but expand the RAM of our hosting plan (if that's the right term for it). This won't fix the memory issue but make it less prevalent. However, it could also reach the point where we're just in the same boat as time goes on. This also has a price tag, and I get the impression that it's not felt to be super efficient. (That is, we're making use of all the RAM, but practically none of the CPU, etc.)
- Try to migrate to a platform like Discourse which has tools for migrating from NodeBB so as to not lose our board history.
- Just start entirely fresh on a different platform and keep the current NodeBB setup live for a given period of time in read-only form.
- Move the database from the current Linode VM to the local machine of a member. I assume this would be paired with keeping the current NodeBB+Redis setup.
- There was a mention at one point wondering if moving to Digital Ocean would be of any help, I think mostly because they have a Discourse-specific droplet setup that should be pretty simple, so that is in the mix somewhere.
Please correct me if I've gotten any of those wrong.
Here are my thoughts, for what they are worth. I am not a mod here, I am just a frequent poster with very strong opinions about everything in the world.
- I think people would absolutely come to regret losing the board history. I know I would. Yes, we would of course all make do without it if it was necessary, but it seems preferable to explore other options before that.
- I am a rare person on MSB who likes NodeBB's style/design, but I would not be heartbroken if it was best for the board to move platforms.
- I absolutely think there are enough people who would pitch in funds that would pay for the migration cost of the first option.
- The idea of moving stuff to one person's local machine makes me weirdly nervous. It feels like a certain loss of control? Unless there's an issue with not having the funds to support a professional hosting solution, which I don't think there are, it seems like a step that could potentially bring its own problems that we don't have right now.
I think 1 or 3 are the most ideal solutions amid all of it. I don't know if there would be any cost savings in moving to Digital Ocean in conjunction with 3, or if it would help reduce the technical lift post-migration since it has that Discourse-specific droplet option. I imagine other folks would have more insight there. I would be absolutely willing to organize a GoFundMe for #1, and/or contribute to one someone else set up. I would also be willing to try and help with #3 with the caveats that I gave up top. I know there was at least a person or two in the thread who indicated that they have experience with database migration stuff and willingness to help.