Reposted by @fastify.devWes @notwes.bsky.social · 29/01/2025@fastify.dev’s logo was a lot harder to try and replicate 🤣. Might need to take a second try on that one. 111
Reposted by @fastify.devIgor "kibertoad" Savin @kibertoad.bsky.social · 23/01/2025It is my absolute pleasure to announce Lokalise launching an OSS support fund. Within the first cohort we are providing monthly funding to @drizzle.team , @biomejs.dev , @fastify.dev and several other projects. Special kudos to @ondrejsevcik.bsky.social for championing this idea until it happened! 073
Reposted by @fastify.devTeslemetry @teslemetry.com · 17/01/2025This week we launched our next-gen API built on @fastify.dev, fully documented with OpenAPI, and with a modular design, which made it easy to implement some new Fleet Telemetry features too. It wasn't the smoothest launch I've done... teslemetry.com/blog/move-fa...teslemetry.comMove fast, break thingsIntroducing the next-gen API and more flexible Fleet Telemetry 021
Reposted by @fastify.devBrett Adams @ba.au · 31/12/2024I just copy pasted a documentation page into @github.com CoPilot with Claude 3.5, and it wrote all the @fastify.dev / OpenAPI schema for me. The time I save using CoPilot far exceeds its cost many times over. 011
fastify.dev @fastify.dev · 11/11/2024Here we are! Ask anything you need about building @nodejs.org APIs. 53617
Reposted by @fastify.devJames Sumners @james.sumners.info · 11/11/2024Yes! HAProxy! Love that thing. I saw so many issues of people “doing it wrong” that I put a guide in to @fastify.dev’s documentation that specifically uses HAProxy, because that’s what people should be using. Not pm2 or whatever other nonsense they’ve cooked up themselves 021
