Soviut

Glad to hear there is some possible movement on this. Regarding consent, I'd imagine there are some provisions if a contributor is unreachable. I mean, if someone passed away it...

@yusukebe I was actually thinking it might be good under this Getting Started section since it already covers a lot of different serverless hosts (Deno, Netlify, Vercel, etc.) 

@yusukebe ```typescript export function main(args: {}): {} { const name: string = args['name'] || 'stranger' const greeting = 'Hello ' + name + '!' return { body: greeting } }...

Also here are the DigitalOcean docs about Node serverless functions and the args that are sent. https://docs.digitalocean.com/products/functions/reference/runtimes/node-js/ ```javascript export function main(event, context) { const name = event.name || 'stranger' const...

@yusukebe I already have an API I built with Hono for CloudFlare that I want to move to DIgitalOcean serverless functions on their "App Platform". Hono is ideal for these...

@yusukebe I managed to get an example working with Hono in a DigitalOcean function. ```typescript import { Hono } from 'hono' const app = new Hono() app.get('/', (c) => c.text('Hello...

@yusukebe yes, it's straightforward but there should definitely be an official adapter since I'm missing things like headers and such.

**EDIT: I just updated to latest (3.22.4) and that fixed this.** I have a similar issue with emails that contain multiple subdomains with the first level subdomain (closest to the...

I think the last option is a good one. It might be worth calling the file simply `routes.ts` so that other router-related things can be defined in it for that...

Correct; all in-memory. And by "Buffer" I mean a binary Buffer or ArrayBuffer in Node. I'm making that distinction because the exporter has a `buffer` mode but it outputs to...