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>
103 lines
3.8 KiB
Plaintext
103 lines
3.8 KiB
Plaintext
# GCP
|
|
|
|
Deploying Cal.diy on Google Cloud Platform (GCP). In this guide, we will go over the steps to deploy Cal.diy on Google Cloud Platform (GCP). We will cover how to create a virtual machine, configure it, install Docker, and finally deploy the Cal.diy application.
|
|
|
|
## One Click Deployment
|
|
|
|
[](https://deploy.cloud.run/?git_repo=https://github.com/calcom/cal.diy)
|
|
|
|
## Manual Deployment
|
|
|
|
### 1. Creating a Virtual Machine
|
|
|
|
#### Go to the GCP Console
|
|
|
|
First, open the Google Cloud Platform console by visiting [https://console.cloud.google.com/](https://console.cloud.google.com/).
|
|
|
|
#### Create a New Project
|
|
|
|
If you haven't already, create a new project by clicking on the "Select a project" dropdown menu and selecting "New Project". Enter a name for your project and click on the "Create" button.
|
|
|
|
#### Create a New VM Instance
|
|
|
|
Click on the navigation menu icon (three horizontal lines) and select "Compute Engine" from the list. Then, click on "VM instances" in the sub-menu. Click on the "Create" button to create a new virtual machine.
|
|
|
|
#### Select the Machine Type
|
|
|
|
Choose the machine type that best suits your needs. Ideally, 2 vCPUs and 2-4GB RAM is enough.
|
|
|
|
#### Set Up Networking
|
|
|
|
Make sure the "Networking" tab is selected and click on the "Add network" button. Choose the "Default" network and click on the "Add" button.
|
|
|
|
#### Create the Instance
|
|
|
|
Review the details of your virtual machine and click on the "Create" button to create the instance. Note the public IP of the VM.
|
|
|
|
### 2. Configuring the Virtual Machine
|
|
|
|
Once your virtual machine is created, you need to configure it to allow traffic on port 80.
|
|
|
|
#### Open Port 80
|
|
|
|
Click on the navigation menu icon (three horizontal lines) and select "Compute Engine" from the list. Then, click on "VM instances" in the sub-menu. Find your newly created instance and click on its name to enter its details page. Click on the "Firewalls" tab and then click on the "Add firewall rule" button. Select "Allow all" as the source and destination, set the protocol to "tcp" and the ports to "80". Click on the "Add" button to save the changes.
|
|
|
|
### 3. Installing Docker
|
|
|
|
Now that your virtual machine is configured, you need to install Docker on it.
|
|
|
|
#### Connect to Your Instance
|
|
|
|
Open a terminal window on your local machine and use SSH to connect to your virtual machine. You can find the external IP address or DNS name of your instance in the GCP console. Use the following command to connect to your instance:
|
|
|
|
```bash
|
|
gcloud ssh --project=[PROJECT_ID] --zone=[ZONE] [INSTANCE_NAME]
|
|
```
|
|
|
|
Replace `[PROJECT_ID]` with your project ID, `[ZONE]` with the zone where your instance is located, and `[INSTANCE_NAME]` with the name of your instance. You can also use web based SSH.
|
|
|
|
#### Install Docker
|
|
|
|
Once connected, update the package list and install Docker using the following commands:
|
|
|
|
```bash
|
|
sudo apt-get update
|
|
sudo apt-get install docker.io
|
|
```
|
|
|
|
#### Start the Docker Service
|
|
|
|
Start the Docker service using the following command:
|
|
|
|
```bash
|
|
sudo systemctl start docker
|
|
```
|
|
|
|
### 4. Deploying Cal.diy
|
|
|
|
Now that Docker is installed and running, you can deploy Cal.diy on your virtual machine.
|
|
|
|
#### Pull the Docker Image
|
|
|
|
Use the following command to pull the Cal.diy Docker image from Docker Hub:
|
|
|
|
```bash
|
|
docker pull calcom/cal.diy
|
|
```
|
|
|
|
#### Run the Docker Container
|
|
|
|
Run the Docker container using the following command:
|
|
|
|
```bash
|
|
docker run -d -p 80:80 calcom/cal.diy
|
|
```
|
|
|
|
This command maps port 80 on your local machine to port 80 inside the container, so you can access Cal.diy from outside the container.
|
|
|
|
#### Access Cal.diy
|
|
|
|
Open a web browser and navigate to `http://localhost`. You should now be able to access the Cal.diy homepage.
|
|
|
|
Congratulations! You have successfully deployed Cal.diy on Google Cloud Platform.
|