as of some time..
./nodebb reset -p nodebb-plugin-pluginName
This is awesome. (Y) Thanks
sn't the RAM requirements of MongoDB a show-stopper for small sites, like those running on a DO 512 droplet? Just curious.
You know -- we've never tried installing Mongo on a 512MB droplet. @baris does his development on a Linode machine with 1GB I think?
@planner I don't quite understand what you mean, so I'm just going to state what I know. I'm currently running my site on a 512 droplet. It runs fine and MongoDB is far from the largest memory consumer, taking up only 34.9 MB. node.js takes up more RAM at 128 MB. On a new installation, Redis would take up less space (obviously, as there would be nothing to store), however Redis will quickly catchup and even pass MongoDB in RAM usage rather quickly. Anyways, now that the facts are out of the way, I have to say it runs fine. Other than taking a little long to load right after a restart, it runs rather speedily.
Thank you, that's good info. Previously, I'd heard from some other place that MongoDB needs 4 GB of RAM for a production site, so the details you provided is good to know. I'll likely be using Mongo for my installation, since it will be sharing resources with 2 WP installations.
@planner To be honest, if you're hosting multiple production sites, I suggest move up to the 1 GB droplet. It would make the whole environment much more stable for not that much more.
I have a 2 GB Droplet, so RAM is not an issue. I just need to find time to optimize php5-fpm to not be a RAM hog.
No Problem @planner