ab21c7f805
* feat: Cal.diy — community-driven MIT-licensed fork of Cal.com This squashed commit contains all Cal.diy changes applied on top of calcom/cal.com main: - Rebrand Cal.com to Cal.diy across the entire codebase - Remove Enterprise Edition (EE) features, license checks, and AGPL restrictions - Switch license from AGPL-3.0 to MIT - Remove docs/ directory (migrated to Nextra at cal.diy) - Remove dead code: org tests, EE tips, platform nav, premium username, SAML/SSO, etc. - Clean up .env.example for self-hosted Cal.diy - Update Docker image references to calcom/cal.diy - Update README, CONTRIBUTING.md, and issue templates for Cal.diy community fork - Add PR welcome bot for Cal.diy contributors - Fix API v2 breaking changes oasdiff ignore entries - Replace Blacksmith CI runners with default GitHub Actions 3893 files changed, 20789 insertions(+), 411020 deletions(-) Co-Authored-By: benny@cal.com <sldisek783@gmail.com> * refactor: remove org-specific /organizations/:orgId endpoints from API v2 atoms controllers (#1701) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> * fix: revert Cal.diy Inc to Cal.com, Inc. in license files, copyright notices, and package metadata (#1702) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> * rip out org related comments in api v2 --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
76 lines
2.0 KiB
Plaintext
76 lines
2.0 KiB
Plaintext
# Vercel
|
|
|
|
## Requirements
|
|
|
|
Currently Vercel Pro Plan is required to be able to Deploy this application with Vercel, due to limitations on the number of serverless functions on the free plan.
|
|
|
|
You need a PostgresDB database hosted somewhere. [Supabase](https://supabase.com) offer a great free option while [Heroku](https://heroku.com) offers a low-cost option.
|
|
|
|
## One Click Deployment
|
|
|
|
[](https://vercel.com/new/clone?repository-url=https://github.com/calcom/cal.diy)
|
|
|
|
## Manual Deployment
|
|
|
|
### Local settings
|
|
|
|
1. **Fork and clone the repository**
|
|
|
|
```bash
|
|
git clone https://github.com/<<your-fork>>/cal.diy.git
|
|
```
|
|
|
|
2. **Set environment variables**
|
|
|
|
Copy the `.env.example` file in `apps/web`, rename it to `.env` and fill it with your settings (See [manual setup](/installation) and Obtaining the Google API Credentials)
|
|
|
|
3. **Install packages with yarn**
|
|
|
|
```bash
|
|
yarn install
|
|
```
|
|
|
|
4. **Set up the database using the Prisma schema**
|
|
|
|
Schema is located in at `packages/prisma/schema.prisma`.
|
|
|
|
```bash
|
|
yarn workspace @calcom/prisma db-deploy
|
|
```
|
|
|
|
5. **Open Prisma Studio**
|
|
|
|
To look at or modify the database content
|
|
|
|
```bash
|
|
yarn db-studio
|
|
```
|
|
|
|
6. **Open User model**
|
|
|
|
Click on the `User` model to add a new user record.
|
|
|
|
7. **Create new user**
|
|
|
|
Fill out the fields (remembering to encrypt your password with [BCrypt](https://bcrypt-generator.com/)) and click `Save 1 Record` to create your first user.
|
|
|
|
8. **Login**
|
|
|
|
Open a browser to port 3000 on your localhost and login with your just created, first user.
|
|
|
|
> Sometimes, yarn install might fail during deployment on Vercel, in which case, you can use `YARN_ENABLE_IMMUTABLE_INSTALLS=false yarn install` as the install command instead.
|
|
|
|
#### Deployment
|
|
|
|
1. Create a new project on Vercel
|
|
2. Import from your forked repository
|
|
3. Set the Environment Variables
|
|
4. Set the root directory to `apps/web`
|
|
5. Override the build command to:
|
|
|
|
```bash
|
|
cd ../.. && yarn build --include-dependencies --no-deps
|
|
```
|
|
|
|
6. Hit Deploy
|