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

[zeluspudding]

In general I have the impression the self hosted versions (I've tried the one click deploy buttons for Heroku and Vercel, as well as building the project from source on Heroku) aren't really meant to be easy to set up... not sure if not by design.

[zomars]

Agreed @zeluspudding that is quite a challenge to keep this as compatible on most services as possible and since we're ourselves using this repo for our SaSS hosted version it can get quite messy sometimes. We cannot just do "whatever we want" to make this work for us and makes all decisions to be made harder because of this. As always we're grateful for improvements that have come from the community on this regard. But definitely it's not by design.

[PeerRich]

maybe @zomars has some tips

[nosovk]

According to screens above it's not intended to be launched on hobby plan
Just merge that #3579 to doc, because now it's a bit misleading.

[zomars]

Quick Q: Wouldn't this be mitigated by #3573 ?

[agustif]

@zomars it would help us reduce our number of /api/ serverless functions, but our bigger problem is translations as each locale gets duplicated and that's how we end up with 1500 serverless functions almost

There has to be a way around it, but not sure if we can keep the /en/ subfolder like structure, or need to change next-i18next for some other 18n lib, or what exactly to fix it... Curious also if this is happening now after we touched some redirects stuff, or has always been the case?

[zomars]

We might need to disable auto locale redirect and implement our own