Fastify logo clay stamp

@fastify.dev’s logo was a lot harder to try and replicate 🤣. Might need to take a second try on that one.

29.01.2025 20:26 — 👍 1    🔁 1    💬 1    📌 0

It 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!

23.01.2025 15:10 — 👍 7    🔁 3    💬 0    📌 0

Move fast, break things Introducing the next-gen API and more flexible Fleet Telemetry

This 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...

17.01.2025 13:16 — 👍 2    🔁 1    💬 0    📌 0

JS if you want to reuse some of the old code. TS if you want the benefit of autocomplete of query/body/etc!

31.12.2024 12:14 — 👍 1    🔁 0    💬 2    📌 0

I 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.

31.12.2024 05:18 — 👍 1    🔁 1    💬 0    📌 0

That’d be interesting to do! What’s the main repository to port?

17.11.2024 11:30 — 👍 5    🔁 0    💬 1    📌 0

Here we are! Ask anything you need about building @nodejs.org APIs.

11.11.2024 15:35 — 👍 37    🔁 17    💬 5    📌 0

Yes! 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

11.11.2024 14:50 — 👍 2    🔁 1    💬 0    📌 0