meetsy VS cal.com

I'm a newbie to django, trying to create a project with DRF and react as front end. Currently i have a react front end with nextjs and next-auth, authenticating through google then passing the token back to django where I have dj-rest-auth setup to login and create user.

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.