flyctl VS cal.com

To begin visit fly.io to create an account. Next install flyctl a command line tool for creating and deploying fly apps. macOS

For frontend deployment, I used Netlify (for the generous free package) and the recommended fly.io for server + database (also cheap package).

Create an account on Fly.io.

You can learn more about fly.io and tigris, we will need to create an account on both platforms for this project regardless. Anyway with the theory out of the way let's get started in the next section as we create our accounts and start building the app.

Fly.io is a platform that helps you run your apps and databases closer to your users all around the world. It takes your app code, packages it up neatly, and puts it on virtual machines that can be quickly started or stopped. This makes your app faster for users and more reliable. Fly.io is easy to use, works well for small projects or personal apps. It's a great way to make sure your app runs smoothly for people no matter where they are.

In this post, we'll start from scratch, running FerretDB locally via Docker, trying out the connection with mongosh and the MongoDB Node.js client, and finally deploy FerretDB to Fly.io for a production ready set up.

2- fly.io

Fly is a cloud platform that focuses on global edge computing. Fly specializes in high-performance hosting and provides a global network of edge locations. Fly is known for its scalability and performance optimizations.

But videototextai.com is built using NextJS + Firebase auth + Firestore and a backend deployed at fly.io . Fly makes it really easy to deploy docker containers and that is IMO the fastest way to develop, you can setup a local setup

Alternatives explored: * northflank: While running the wrk test, requests were taking 3-7 seconds. Couldn't repeat Heroku's phenomenon of "400ms-800ms" during such a load test. * fly.io: Reliability: It’s Not Great * render.com: I remember the time when indiehackers.com was down because of an outage on Render, not sure if it's worth trusting.

Cal.com is an open-source event-juggling scheduler for everyone, and is free for individuals.

Turborepo is a tool that makes it easy to manage monorepos with pnpm and typescript. On large open source porject like cal.com they use it for fast building or running developing tasks like testing or linting. Turborepo depend havily on caching so it would reduce signficantly the time to build or run the tasks as well as CI/CD pipelines time and cost.

The next codebase to analyse is cal.com. This repo is larger than jsoncrack. It is a monorepo with packages and lots of stuff going behind the scenes.

hey, peer here from cal.com. we have an issue where we track all individual caldav implementations: https://github.com/calcom/cal.com/issues/9990

Cal - Alternative to Calendly

I force clients who want to talk to me to book a call. I use cal.com (free) and my Google Calendar (which its linked to) only allows calls on specific days/times. I have a few "Call Blocks" where they can book. That let's me do calls in a small section of my week, with ample downtime to recover the rest of the week. I'm still learning how many calls a day I can handle. Currently anything more than 2 is too much.

Cal.com- Cal.com is a scheduling tool that helps you schedule meetings without the back-and-forth emails.

Peer Rich (CEO at Cal.com)

Has any one deployed cal.com with selfhosted environment. Is yes how would have configured prisma for the same.

Recently I came across a company called cal.com, it's a Calendly alternative, but the catch is the entire software is open source: https://github.com/calcom/cal.com.