infra-deploy_skill

This skill deploys Cal.com self-hosted to GCP Cloud Run with Supabase PostgreSQL, enabling automated infra setup and scalable hosting.

TypeScript

14

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill terrylica/cc-skills --skill infra-deploy

SKILL.md7.6 KB

Overview

This skill automates deployment of a self-hosted Cal.com instance to GCP Cloud Run with a Supabase PostgreSQL backend and provides a Docker Compose setup for local development. It bundles Cloud Run build/push/deploy steps, webhook relay deployment for Pushover alerts, and database migration helpers. The goal is repeatable, secure deployments using 1Password for secrets and standard gcloud/docker tooling.

How this skill works

The skill checks required GCP and Supabase configuration and validates 1Password secret references before proceeding. It builds a Docker image, pushes it to Google Artifact Registry, and deploys to Cloud Run with environment variables sourced from 1Password. For local workflows it supplies a Docker Compose template and .env examples. It also includes a lightweight webhook relay service deployable to Cloud Run for Pushover notifications and helpers to run Prisma migrations against Supabase.

When to use it

Deploy Cal.com to GCP Cloud Run for managed, autoscaled hosting.
Run Cal.com locally for development using Docker Compose and Postgres.
Add emergency notifications by deploying the Pushover webhook relay.
Perform database connectivity checks or run Prisma migrations on Supabase.
Automate CI/CD pipelines that require Artifact Registry and Cloud Build integration.

Best practices

Store all sensitive values in 1Password and reference them via op read; never commit secrets to repo.
Validate gcloud authentication and enabled APIs (Cloud Run, Artifact Registry, Cloud Build) before builds.
Tag Docker images with region/project-aware Artifact Registry names to avoid push failures.
Keep Cloud Run env vars minimal and set public URLs explicitly (NEXT_PUBLIC_*).
Run migrations against the Supabase DATABASE_URL before switching traffic to a new release.

Example use cases

CI job: build Docker image, push to Artifact Registry, and deploy to Cloud Run with env vars from 1Password.
Local development: run docker-compose to spin up Cal.com and a Postgres instance for feature testing.
On-call flow: deploy the webhook-relay Cloud Run service to forward critical booking events to Pushover.
Database ops: verify Supabase connection and run prisma migrate deploy after schema changes.
Staging preview: deploy a separate GCP project/Cloud Run service for testing before production rollout.

FAQ

NEXTAUTH_SECRET, CALENDSO_ENCRYPTION_KEY, CRON_API_KEY, and DATABASE_URL must be stored in the Claude Automation 1Password vault and referenced with op.

Which GCP APIs must be enabled?

Enable Cloud Run, Artifact Registry, and Cloud Build for the target GCP project and account.

How do I test the webhook relay?

Deploy the relay, note the service URL, curl the URL with a simulated BOOKING_CREATED payload, and confirm a Pushover alert is received.