Deploy to Vercel seems to be broken for free plan

[nosovk]

Issue Summary

I've created a new deployment of cal.com, but it seems to be broken.

Steps to Reproduce

1. Fork Project
2. Connect to Vercel
3. setup custom build options

4. Build Get response form build system: No more than 12 Serverless Functions can be added to a Deployment on the Hobby plan

[nosovk]

It seems that it was broken some time before, I found the same problem here

[sagararyal]

@nosovk
I don't think it will run on free plan due to serverless function size, as i get the following error on the pro plan:

however few other things that can be documented well:

You need to change your build code, either remove the root dir, or remove cd ../.. from the build command. I had to try this several times until a successful build.

the other thing i had to add as I am using supabase is

• append ?pgbouncer=true to database url.
• add env PGSSLMODE = no-verify

[nosovk]

According to docs serverless-function-size is the same for all plans, and came due to underlain AWS. In common config proposed by you seems to be more logical compared to one from docs.

[sagararyal]

@nosovk True the size seems to be same. Then someone needs to reduce the count of serverless functions; which seems to be impossible in this project as there are 1370 serverless functions (mostly language based pages) so the real number is around 40 or so. Vercel limit for hobby plan is 12.
https://vercel.com/docs/concepts/limits/overview#serverless-functions-created-per-deployment

Regarding build: After my first successful build, i was also able to build successfully using the cd ../.. build code along with the custom directory. Not sure what the difference is.

Update:
I believe the goal of cd ../.. && yarn build is to deploy prisma build commands and populate seed-app-store.

[nosovk]

Probably should mention in docs that free vercel is not ok to host cal.com