Stable for years. Actual open governance so no more startup bait and switch. https://arc.codes. - Source: Hacker News / 24 days ago

I had been running dockeri.co with https://arc.codes/ for pennies a month. Then, one month, I got a ~$500 bill out of no where. Docker had changed an api causing my service to return 5xx errors all month. Each error was individually logged to CloudWatch - which racked up a ~$500 bill. I moved to Cloudflare Workers that day and haven’t moved back. - Source: Hacker News / 9 months ago

I use https://arc.codes/ for deploying to AWS Lambda/API Gateway. It does a really good job with Remix and NestJS and is easy enough. I like that all I have to do is give a very simple config, and it builds the apps, zips the function code, uploads all my static assets, and then generates and deploys the CloudFormation. I am curious to migrate off as I do have to do some workarounds and it doesn't seem to have a... Source: 12 months ago

Not sure why this is downvoted, Fastify is quite popular and the 'generator for everything' approach of Koa didn't really take off. Architect serverless (https://arc.codes) is pretty good for serverless. - Source: Hacker News / about 1 year ago

Architect is a heavily opinionated framework for building FWA's, Functional Web Apps. It uses AWS SAM under the hood but provides a layer on top with simplified abstractions that lets developers define and use AWS infrastructure without necessarily knowing what service is backing their "events" construct. - Source: dev.to / over 1 year ago

You’re likely looking for the events api. Source: over 1 year ago

If you're familiar with the existing Events API, you may be confused with some differences between this next-generation platform's event triggers and Events API. - Source: dev.to / over 1 year ago

For a more generic approach (if you want to get pretty much everything going on in Slack) you can use the https://api.slack.com/apis/connections/events-api. This approach will also result in getting POST requests from Slack which n8n can handle. Source: over 1 year ago

Slack’s API is massive (at least for someone like me, an accountant) if you are not familiar with it, then option 1 could be a little complicated. I think for option 1 you could use either Slack’s Event’s API or Slack’s webhook, that would depend on your Slack’s workspace set up https://api.slack.com/apis/connections/events-api. Also, you will need to create an app in Slack (with the required Oauth credentials and... Source: over 1 year ago

How let's explore another highly common use case for your bot: Handling mentions. Slacks enables mentions via the subscription of events. The Events API is a streamlined, easy way to build bots that responds to activities in Slack. - Source: dev.to / about 2 years ago