Open-source status page, incident response and uptime monitoring
TypeScript alertingincident-managementmcpmcp-servermonitoringmonitoring-as-codeobservabilityon-callopen-sourcesrestatus-pagestatuspagesynthetic-monitoringterraformtinybirdtursouptimeuptime-checkeruptime-monitor
Update migration-backend-from-vercel-to-fly.mdx (#423)
Stephan de Vries46859c291247
diff --git a/apps/web/src/content/posts/migration-backend-from-vercel-to-fly.mdx b/apps/web/src/content/posts/migration-backend-from-vercel-to-fly.mdxindex 90fa41000..77ffeea42 100644--- a/apps/web/src/content/posts/migration-backend-from-vercel-to-fly.mdx+++ b/apps/web/src/content/posts/migration-backend-from-vercel-to-fly.mdx@@ -114,7 +114,7 @@ I wish it had been documented elsewhere.We are pleased with our migration to Fly.io, although it was accompanied by achallenging weekend. And we still love Vercel, they offer a super product, it-removes a lot of pain for the developers.However, if you require a hosting an+removes a lot of pain for the developers. However, if you require a hosting anapplication other than Next.js, it may not be the best option.We are still using it for our frontend.