Has anyone tried deploying Nodebb with the Serverless Framework in Lambda?

Right now, I have a t2.small instance running NodeBB and the MongoDB. It was on a t2.micro, but that thing doesn't have swap and when it ran out of memory, it crashed. t2.small doesn't have swap either, but it has more memory and has been stable. I'm paying about $20/mo in AWS costs, and I'm looking to reduce those costs.

So, I was thinking if I could deploy NodeBB in Lambda, it could reduce costs there. However, I still have the problem of having to run MongoDB. I think it would still need to run in t2.small instance, so it wouldn't save me any money by doing this. And AWS DocumentDB (which is mongo compatible) is tied to EC2 instances, and the smallest available is much more expensive than a t2.small.

I could also deploy as a docker container, but again, those are tied to an EC2 instance. My first goal is to reduce costs, but my second goal is to do it with an architecture that can scale if I need it to.

Any ideas?

I'm looking to upgrade from 0.10.x to 0.11.x. Is there a script or something which will tell me what plugins are not designed for 0.11.x?

@Julian-H-Lam , what am I doing wrong here? Is this format correct?

I've also tried using CURL, and that also crashes it.

curl --request PUT --header "Authorization: Bearer xxxxx" --header "Content-Type: application/json" --data '{"tags":"test1"}' --verbose https://myforum.com/api/v2/topics/11983/tags

I'm doing a PUT against https://myforum.com/api/v2/topics/11693/tags

I'm trying to put the following content as application/json:

{
  "tags": ["test1", "test2"]
}

When I do this, nodebb immediately crashes with a "callFn.apply is not a function" error message. Is the write API even compatible with v1.10.1?

I noticed there are 2 write API plugins available. I used the one without -tmnl at the end of it. Should I be using that one instead?

https://github.com/NodeBB/nodebb-plugin-write-api/blob/master/routes/v2/readme.md

I'm looking at using the /topics/tag route to add some tags to a ton of topics. This documentation doesn't tell me what's required for updating tags. This is the JSON I get back from the built-in read only API:

      "tags": [
        {
          "color": "",
          "bgColor": "",
          "valueEscaped": "juniper",
          "score": 3,
          "value": "juniper"
        },
        {
          "color": "",
          "bgColor": "",
          "valueEscaped": "ipv6",
          "score": 1,
          "value": "ipv6"
        }
      ],

Can I just submit something like:

      "tags": [
        {
          "value": "somenewtag"
        },
        {
          "value": "anothernewtag"
        }
      ],

I want to stop sending email to addresses that bounce. Either opting the account out of all email, and/or disabling all email notifications.

I'm sending mail via AWS SES, and if your bounce percentage goes above a certain threshold, they will stop you from sending. I need to be able to minimize this as much as possible.

Also, it would be nice to have an unsubscribe link in the email that would automatically unsubscribe users with just one click instead of making them log into their account.

How are others handling this?

Is this possible with just a CSS change, or is it more than that. Because the description is disappearing when making a category into a sub-category, I'm thinking it's more than just CSS.

Install Google Analytics and check there. I'm seeing the same thing, most of that extra traffic is search engines/bots. Google Analytics ignores them and gets you only meat user data.

If needed, is there a way to convert SSO accounts to local ones? Obviously they would require a password reset.