GitHub Trending Today for typescript - TypeScript Daily

umami-software/umami

Sun, 09 Nov 2025 00:05:03 GMT

umami-software/umami

Umami is a modern, privacy-focused alternative to Google Analytics.

Language: TypeScript

Stars: 32,300

Forks: 5,791

Stars today: 294 stars today

README

Umami

Umami is a simple, fast, privacy-focused alternative to Google Analytics.

--- ## 🚀 Getting Started A detailed getting started guide can be found at [umami.is/docs](https://umami.is/docs/). --- ## 🛠 Installing from Source ### Requirements - A server with Node.js version 18.18 or newer - A database. Umami supports [PostgreSQL](https://www.postgresql.org/) (minimum v12.14) databases. ### Get the Source Code and Install Packages ```bash git clone https://github.com/umami-software/umami.git cd umami pnpm install ``` ### Configure Umami Create an `.env` file with the following: ```bash DATABASE_URL=connection-url ``` The connection URL format: ```bash postgresql://username:mypassword@localhost:5432/mydb ``` ### Build the Application ```bash pnpm run build ``` _The build step will create tables in your database if you are installing for the first time. It will also create a login user with username **admin** and password **umami**._ ### Start the Application ```bash pnpm run start ``` _By default, this will launch the application on `http://localhost:3000`. You will need to either [proxy](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/) requests from your web server or change the [port](https://nextjs.org/docs/api-reference/cli#production) to serve the application directly._ --- ## 🐳 Installing with Docker To build the Umami container and start up a Postgres database, run: ```bash docker compose up -d ``` Alternatively, to pull just the Umami Docker image with PostgreSQL support: ```bash docker pull docker.umami.is/umami-software/umami:latest ``` --- ## 🔄 Getting Updates > [!WARNING] > If you are updating from Umami V2, image "postgresql-latest" is deprecated. You must change it to "latest". > e.g., rename `docker.umami.is/umami-software/umami:postgresql-latest` to `docker.umami.is/umami-software/umami:latest`. To get the latest features, simply do a pull, install any new dependencies, and rebuild: ```bash git pull pnpm install pnpm run build ``` To update the Docker image, simply pull the new images and rebuild: ```bash docker compose pull docker compose up --force-recreate -d ``` --- ## 🛟 Support

[release-shield]: https://img.shields.io/github/release/umami-software/umami.svg [releases-url]: https://github.com/umami-software/umami/releases [license-shield]: https://img.shields.io/github/license/umami-software/umami.svg [license-url]: https://github.com/umami-software/umami/blob/master/LICENSE [build-shield]: https://img.shields.io/github/actions/workflow/status/umami-software/umami/ci.yml [build-url]: https://github.com/umami-software/umami/actions [github-shield]: https://img.shields.io/badge/GitHub--blue?style=social&logo=github [github-url]: https://github.com/umami-software/umami [twitter-shield]: https://img.shields.io/badge/Twitter--blue?style=social&logo=twitter [twitter-url]: https://twitter.com/umami_software [linkedin-shield]: https://img.shields.io/badge/LinkedIn--blue?style=social&logo=linkedin [linkedin-url]: https://linkedin.com/company/umami-software [discord-shield]: https://img.shields.io/badge/Discord--blue?style=social&logo=discord [discord-url]: https://discord.com/invite/4dz4zcXYrQ

nocobase/nocobase

Sun, 09 Nov 2025 00:05:02 GMT

nocobase/nocobase

NocoBase is the most extensible AI-powered no-code/low-code platform for building business applications and enterprise solutions.

Language: TypeScript

Stars: 18,919

Forks: 2,118

Stars today: 125 stars today

README

English | [中文](./README.zh-CN.md) | [日本語](./README.ja-JP.md) https://github.com/user-attachments/assets/4d11a87b-00e2-48f3-9bf7-389d21072d13

Build and deploy AI agent workflows in minutes.

## Quickstart ### Cloud-hosted: [sim.ai](https://sim.ai) ### Self-hosted: NPM Package ```bash npx simstudio ``` → http://localhost:3000 #### Note Docker must be installed and running on your machine. #### Options | Flag | Description | |------|-------------| | `-p, --port ` | Port to run Sim on (default `3000`) | | `--no-pull` | Skip pulling latest Docker images | ### Self-hosted: Docker Compose ```bash # Clone the repository git clone https://github.com/simstudioai/sim.git # Navigate to the project directory cd sim # Start Sim docker compose -f docker-compose.prod.yml up -d ``` Access the application at [http://localhost:3000/](http://localhost:3000/) #### Using Local Models with Ollama Run Sim with local AI models using [Ollama](https://ollama.ai) - no external APIs required: ```bash # Start with GPU support (automatically downloads gemma3:4b model) docker compose -f docker-compose.ollama.yml --profile setup up -d # For CPU-only systems: docker compose -f docker-compose.ollama.yml --profile cpu --profile setup up -d ``` Wait for the model to download, then visit [http://localhost:3000](http://localhost:3000). Add more models with: ```bash docker compose -f docker-compose.ollama.yml exec ollama ollama pull llama3.1:8b ``` ### Self-hosted: Dev Containers 1. Open VS Code with the [Remote - Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) 2. Open the project and click "Reopen in Container" when prompted 3. Run `bun run dev:full` in the terminal or use the `sim-start` alias - This starts both the main application and the realtime socket server ### Self-hosted: Manual Setup **Requirements:** - [Bun](https://bun.sh/) runtime - PostgreSQL 12+ with [pgvector extension](https://github.com/pgvector/pgvector) (required for AI embeddings) **Note:** Sim uses vector embeddings for AI features like knowledge bases and semantic search, which requires the `pgvector` PostgreSQL extension. 1. Clone and install dependencies: ```bash git clone https://github.com/simstudioai/sim.git cd sim bun install ``` 2. Set up PostgreSQL with pgvector: You need PostgreSQL with the `vector` extension for embedding support. Choose one option: **Option A: Using Docker (Recommended)** ```bash # Start PostgreSQL with pgvector extension docker run --name simstudio-db \ -e POSTGRES_PASSWORD=your_password \ -e POSTGRES_DB=simstudio \ -p 5432:5432 -d \ pgvector/pgvector:pg17 ``` **Option B: Manual Installation** - Install PostgreSQL 12+ and the pgvector extension - See [pgvector installation guide](https://github.com/pgvector/pgvector#installation) 3. Set up environment: ```bash cd apps/sim cp .env.example .env # Configure with required variables (DATABASE_URL, BETTER_AUTH_SECRET, BETTER_AUTH_URL) ``` Update your `.env` file with the database URL: ```bash DATABASE_URL="postgresql://postgres:your_password@localhost:5432/simstudio" ``` 4. Set up the database: First, configure the database package environment: ```bash cd packages/db cp .env.example .env ``` Update your `packages/db/.env` file with the database URL: ```bash DATABASE_URL="postgresql://postgres:your_password@localhost:5432/simstudio" ``` Then run the migrations: ```bash bunx drizzle-kit migrate --config=./drizzle.config.ts ``` 5. Start the development servers: **Recommended approach - run both servers together (from project root):** ```bash bun run dev:full ``` This starts both the main Next.js application and the realtime socket server required for full functionality. **Alternative - run servers separately:** Next.js app (from project root): ```bash bun run dev ``` Realtime socket server (from `apps/sim` directory in a separate terminal): ```bash cd apps/sim bun run dev:sockets ``` ## Copilot API Keys Copilot is a Sim-managed service. To use Copilot on a self-hosted instance: - Go to https://sim.ai → Settings → Copilot and generate a Copilot API key - Set `COPILOT_API_KEY` environment variable in your self-hosted apps/sim/.env file to that value ## Tech Stack - **Framework**: [Next.js](https://nextjs.org/) (App Router) - **Runtime**: [Bun](https://bun.sh/) - **Database**: PostgreSQL with [Drizzle ORM](https://orm.drizzle.team) - **Authentication**: [Better Auth](https://better-auth.com) - **UI**: [Shadcn](https://ui.shadcn.com/), [Tailwind CSS](https://tailwindcss.com) - **State Management**: [Zustand](https://zustand-demo.pmnd.rs/) - **Flow Editor**: [ReactFlow](https://reactflow.dev/) - **Docs**: [Fumadocs](https://fumadocs.vercel.app/) - **Monorepo**: [Turborepo](https://turborepo.org/) - **Realtime**: [Socket.io](https://socket.io/) - **Background Jobs**: [Trigger.dev](https://trigger.dev/) - **Remote Code Execution**: [E2B](https://www.e2b.dev/) ## Contributing We welcome contributions! Please see our [Contributing Guide](.github/CONTRIBUTING.md) for details. ## License This project is licensed under the Apache License 2.0 - see the [LICENSE](LICENSE) file for details.

Made with ❤️ by the Sim Team

open-metadata/OpenMetadata

Sun, 09 Nov 2025 00:04:56 GMT

open-metadata/OpenMetadata

OpenMetadata is a unified metadata platform for data discovery, data observability, and data governance powered by a central metadata repository, in-depth column level lineage, and seamless team collaboration.

Language: TypeScript

Stars: 7,919

Forks: 1,509

Stars today: 8 stars today

README

Empower your Data Journey with OpenMetadata

![Commit Activity](https://img.shields.io/github/commit-activity/m/open-metadata/OpenMetadata?style=for-the-badge) [![Release](https://img.shields.io/github/release/open-metadata/OpenMetadata/all.svg?style=for-the-badge)](https://github.com/open-metadata/OpenMetadata/releases)

## What is OpenMetadata? [OpenMetadata](https://open-metadata.org/) is a unified metadata platform for data discovery, data observability, and data governance powered by a central metadata repository, in-depth column level lineage, and seamless team collaboration. It is one of the fastest-growing open-source projects with a vibrant community and adoption by a diverse set of companies in a variety of industry verticals. Based on Open Metadata Standards and APIs, supporting connectors to a wide range of data services, OpenMetadata enables end-to-end metadata management, giving you the freedom to unlock the value of your data assets.

Contents: - [Features](#key-features-of-openmetadata) - [Try our Sandbox](#try-our-sandbox) - [Install & Run](#install-and-run-openmetadata) - [Roadmap](https://docs.open-metadata.org/latest/roadmap) - [Documentation and Support](#documentation-and-support) - [Contributors](#contributors) OpenMetadata Consists of Four Main Components: - **Metadata Schemas**: These are the core definitions and vocabulary for metadata based on common abstractions and types. They also allow for custom extensions and properties to suit different use cases and domains. - **Metadata Store**: This is the central repository for storing and managing the metadata graph, which connects data assets, users, and tool-generated metadata in a unified way. - **Metadata APIs**: These are the interfaces for producing and consuming metadata, built on top of the metadata schemas. They enable seamless integration of user interfaces and tools, systems, and services with the metadata store. - **Ingestion Framework**: This is a pluggable framework for ingesting metadata from various sources and tools to the metadata store. It supports about 84+ connectors for data warehouses, databases, dashboard services, messaging services, pipeline services, and more. ## Key Features of OpenMetadata **Data Discovery**: Find and explore all your data assets in a single place using various strategies, such as keyword search, data associations, and advanced queries. You can search across tables, topics, dashboards, pipelines, and services. ![12](https://github.com/open-metadata/OpenMetadata/assets/40225091/0dbd2746-c93d-4a47-8d3e-ceb3ae01436f)

**Data Collaboration**: Communicate, converse, and cooperate with other users and teams on data assets. You can get event notifications, send alerts, add announcements, create tasks, and use conversation threads. ![11](https://github.com/open-metadata/OpenMetadata/assets/40225091/7df29e12-8a29-44b7-9466-42474823783f)

**Data Quality and Profiler**: Measure and monitor the quality with **no-code** to build trust in your data. You can define and run data quality tests, group them into test suites, and view the results in an interactive dashboard. With powerful collaboration, make data quality a shared responsibility in your organization. ![8](https://github.com/open-metadata/OpenMetadata/assets/40225091/6b330827-cc2d-4d06-abf0-a4d42ce532ba)

**Data Governance**: Enforce data policies and standards across your organization. You can define data domains and data products, assign owners and stakeholders, and classify data assets using tags and terms. Use powerful automation features to auto-classify your data. ![10](https://github.com/open-metadata/OpenMetadata/assets/40225091/f7384a71-6b58-44ad-983f-e302718ee3f1)

**Data Insights and KPIs**: Use reports and platform analytics to understand how your organization's data is doing. Data Insights provides a single-pane view of all the key metrics to reflect the state of your data best. Define the Key Performance Indicators (KPIs) and set goals within OpenMetadata to work towards better documentation, ownership, and tiering. Alerts can be set against the KPIs to be received on a specified schedule. ![9](https://github.com/open-metadata/OpenMetadata/assets/40225091/61fc2f65-2436-4fc9-9434-c27ee9b25183)

**Data Lineage**: Track and visualize the origin and transformation of your data assets end-to-end. You can view column-level lineage, filter queries, and edit lineage manually using a no-code editor. **Data Documentation**: Document your data assets and metadata entities using rich text, images, and links. You can also add comments and annotations and generate data dictionaries and data catalogs. **Data Observability**: Monitor the health and performance of your data assets and pipelines. You can view metrics such as data freshness, data volume, data quality, and data latency. You can also set up alerts and notifications for any anomalies or failures. **Data Security**: Secure your data and metadata using various authentication and authorization mechanisms. You can integrate with different identity providers for single sign-on and define roles and policies for access control. **Webhooks**: Integrate with external applications and services using webhooks. You can register URLs to receive metadata event notifications and integrate with Slack, Microsoft Teams, and Google Chat. **Connectors**: Ingest metadata from various sources and tools using connectors. OpenMetadata supports about 84+ connectors for data warehouses, databases, dashboard services, messaging services, pipeline services, and more. ## Try our Sandbox Take a look and play with sample data at [http://sandbox.open-metadata.org](http://sandbox.open-metadata.org) ## Install and Run OpenMetadata Get up and running in a few minutes. See the OpenMetadata documentation for [installation instructions](https://docs.open-metadata.org/quick-start/local-docker-deployment). ## Documentation and Support We're here to help and make OpenMetadata even better! Check out [OpenMetadata documentation](https://docs.open-metadata.org/) for a complete description of OpenMetadata's features. Join our [Slack Community](https://slack.open-metadata.org/) to get in touch with us if you want to chat, need help, or discuss new feature requirements. ## Contributors We ❤️ all contributions, big and small! Check out our [CONTRIBUTING](./CONTRIBUTING.md) guide to get started, and let us know how we can help. Don't want to miss anything? Give the project a ⭐ 🚀 A HUGE THANK YOU to all our supporters! ## Stargazers [![Stargazers of @open-metadata/OpenMetadata repo](http://reporoster.com/stars/open-metadata/OpenMetadata)](https://github.com/open-metadata/OpenMetadata/stargazers) ## License OpenMetadata is released under [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0)

NginxProxyManager/nginx-proxy-manager

Sun, 09 Nov 2025 00:04:55 GMT

NginxProxyManager/nginx-proxy-manager

Docker container for managing Nginx proxy hosts with a simple, powerful interface

Language: TypeScript

Stars: 29,308

Forks: 3,365

Stars today: 39 stars today

README

This project comes as a pre-built docker image that enables you to easily forward to your websites running at home or otherwise, including free SSL, without having to know too much about Nginx or Letsencrypt. - [Quick Setup](#quick-setup) - [Full Setup](https://nginxproxymanager.com/setup/) - [Screenshots](https://nginxproxymanager.com/screenshots/) ## Project Goal I created this project to fill a personal need to provide users with an easy way to accomplish reverse proxying hosts with SSL termination and it had to be so easy that a monkey could do it. This goal hasn't changed. While there might be advanced options they are optional and the project should be as simple as possible so that the barrier for entry here is low. ## Features - Beautiful and Secure Admin Interface based on [Tabler](https://tabler.github.io/) - Easily create forwarding domains, redirections, streams and 404 hosts without knowing anything about Nginx - Free SSL using Let's Encrypt or provide your own custom SSL certificates - Access Lists and basic HTTP Authentication for your hosts - Advanced Nginx configuration available for super users - User management, permissions and audit log ## Hosting your home network I won't go in to too much detail here but here are the basics for someone new to this self-hosted world. 1. Your home router will have a Port Forwarding section somewhere. Log in and find it 2. Add port forwarding for port 80 and 443 to the server hosting this project 3. Configure your domain name details to point to your home, either with a static ip or a service like DuckDNS or [Amazon Route53](https://github.com/jc21/route53-ddns) 4. Use the Nginx Proxy Manager as your gateway to forward to your other web based services ## Quick Setup 1. Install Docker and Docker-Compose - [Docker Install documentation](https://docs.docker.com/install/) - [Docker-Compose Install documentation](https://docs.docker.com/compose/install/) 2. Create a docker-compose.yml file similar to this: ```yml services: app: image: 'docker.io/jc21/nginx-proxy-manager:latest' restart: unless-stopped ports: - '80:80' - '81:81' - '443:443' volumes: - ./data:/data - ./letsencrypt:/etc/letsencrypt ``` This is the bare minimum configuration required. See the [documentation](https://nginxproxymanager.com/setup/) for more. 3. Bring up your stack by running ```bash docker compose up -d ``` 4. Log in to the Admin UI When your docker container is running, connect to it on port `81` for the admin interface. Sometimes this can take a little bit because of the entropy of keys. [http://127.0.0.1:81](http://127.0.0.1:81) ## Contributing All are welcome to create pull requests for this project, against the `develop` branch. Official releases are created from the `master` branch. CI is used in this project. All PR's must pass before being considered. After passing, docker builds for PR's are available on dockerhub for manual verifications. Documentation within the `develop` branch is available for preview at [https://develop.nginxproxymanager.com](https://develop.nginxproxymanager.com) ### Contributors Special thanks to [all of our contributors](https://github.com/NginxProxyManager/nginx-proxy-manager/graphs/contributors). ## Getting Support 1. [Found a bug?](https://github.com/NginxProxyManager/nginx-proxy-manager/issues) 2. [Discussions](https://github.com/NginxProxyManager/nginx-proxy-manager/discussions) 3. [Reddit](https://reddit.com/r/nginxproxymanager)

blakeblackshear/frigate

Sun, 09 Nov 2025 00:04:54 GMT

blakeblackshear/frigate

NVR with realtime local object detection for IP cameras

Language: TypeScript

Stars: 26,938

Forks: 2,490

Stars today: 149 stars today

README

# Frigate - NVR With Realtime Object Detection for IP Cameras \[English\] | [简体中文](https://github.com/blakeblackshear/frigate/blob/dev/README_CN.md) A complete and local NVR designed for [Home Assistant](https://www.home-assistant.io) with AI object detection. Uses OpenCV and Tensorflow to perform realtime object detection locally for IP cameras. Use of a GPU, Integrated GPU, or AI accelerator such as a [Hailo](https://hailo.ai/) is highly recommended. Dedicated hardware will outperform even the best CPUs with very little overhead. - Tight integration with Home Assistant via a [custom component](https://github.com/blakeblackshear/frigate-hass-integration) - Designed to minimize resource use and maximize performance by only looking for objects when and where it is necessary - Leverages multiprocessing heavily with an emphasis on realtime over processing every frame - Uses a very low overhead motion detection to determine where to run object detection - Object detection with TensorFlow runs in separate processes for maximum FPS - Communicates over MQTT for easy integration into other systems - Records video with retention settings based on detected objects - 24/7 recording - Re-streaming via RTSP to reduce the number of connections to your camera - WebRTC & MSE support for low-latency live view ## Documentation View the documentation at https://docs.frigate.video ## Donations If you would like to make a donation to support development, please use [Github Sponsors](https://github.com/sponsors/blakeblackshear). ## Screenshots ### Live dashboard

### Streamlined review workflow

### Multi-camera scrubbing

### Built-in mask and zone editor

Better Auth

The most comprehensive authentication framework for TypeScript
Learn more »

Discord · Website · Issues

[![npm](https://img.shields.io/npm/dm/better-auth?style=flat&colorA=000000&colorB=000000)](https://npm.chart.dev/better-auth?primary=neutral&gray=neutral&theme=dark) [![npm version](https://img.shields.io/npm/v/better-auth.svg?style=flat&colorA=000000&colorB=000000)](https://www.npmjs.com/package/better-auth) [![GitHub stars](https://img.shields.io/github/stars/better-auth/better-auth?style=flat&colorA=000000&colorB=000000)](https://github.com/better-auth/better-auth/stargazers)

![npm version](https://img.shields.io/npm/v/effect)

# Effect Monorepo

> An ecosystem of tools to build robust applications in TypeScript

## Introduction

Welcome to Effect, a powerful TypeScript framework that provides a fully-fledged functional effect system with a rich standard library.

Effect consists of several packages that work together to help build robust TypeScript applications. The core package, `effect`, serves as the foundation of the framework, offering primitives for managing side effects, ensuring type safety, and supporting concurrency.

## Monorepo Structure

The Effect monorepo is organized into multiple packages, each extending the core functionality. Below is an overview of the packages included:

| Package                           | Description                                                                                 |                                                                                                    |
| --------------------------------- | ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| `effect`                          | Core package                                                                                | [README](https://github.com/Effect-TS/effect/blob/main/packages/effect/README.md)                  |
| `@effect/ai`                      | AI utilities                                                                                | [README](https://github.com/Effect-TS/effect/blob/main/packages/ai/ai/README.md)                   |
| `@effect/ai-openai`               | OpenAI utilities                                                                            | [README](https://github.com/Effect-TS/effect/blob/main/packages/ai/openai/README.md)               |
| `@effect/ai-anthropic`            | Anthropic utilities                                                                         | [README](https://github.com/Effect-TS/effect/blob/main/packages/ai/anthropic/README.md)            |
| `@effect/ai-amazon-bedrock`       | Effect modules for working with Amazon Bedrock AI apis                                      | [README](https://github.com/Effect-TS/effect/blob/main/packages/ai/amazon-bedrock/README.md)       |
| `@effect/ai-google`               | Effect modules for working with Google AI apis                                              | [README](https://github.com/Effect-TS/effect/blob/main/packages/ai/google/README.md)               |
| `@effect/cli`                     | CLI utilities                                                                               | [README](https://github.com/Effect-TS/effect/blob/main/packages/cli/README.md)                     |
| `@effect/cluster`                 | Distributed computing tools                                                                 | [README](https://github.com/Effect-TS/effect/blob/main/packages/cluster/README.md)                 |
| `@effect/experimental`            | Experimental features and APIs                                                              | [README](https://github.com/Effect-TS/effect/blob/main/packages/experimental/README.md)            |
| `@effect/opentelemetry`           | [OpenTelemetry](https://opentelemetry.io/) integration                                      | [README](https://github.com/Effect-TS/effect/blob/main/packages/opentelemetry/README.md)           |
| `@effect/platform`                | Cross-platform runtime utilities                                                            | [README](https://github.com/Effect-TS/effect/blob/main/packages/platform/README.md)                |
| `@effect/platform-browser`        | Platform utilities for the browser                                                          | [README](https://github.com/Effect-TS/effect/blob/main/packages/platform-browser/README.md)        |
| `@effect/platform-bun`            | Platform utilities for [Bun](https://bun.sh/)                                               | [README](https://github.com/Effect-TS/effect/blob/main/packages/platform-bun/README.md)            |
| `@effect/platform-node`           | Platform utilities for [Node.js](https://nodejs.org)                                        | [README](https://github.com/Effect-TS/effect/blob/main/packages/platform-node/README.md)           |
| `@effect/platform-node-shared`    | Shared utilities for [Node.js](https://nodejs.org)                                          | [README](https://github.com/Effect-TS/effect/blob/main/packages/platform-node-shared/README.md)    |
| `@effect/printer`                 | General-purpose printing utilities                                                          | [README](https://github.com/Effect-TS/effect/blob/main/packages/printer/README.md)                 |
| `@effect/printer-ansi`            | ANSI-compatible printing utilities                                                          | [README](https://github.com/Effect-TS/effect/blob/main/packages/printer-ansi/README.md)            |
| `@effect/rpc`                     | Remote procedure call (RPC) utilities                                                       | [README](https://github.com/Effect-TS/effect/blob/main/packages/rpc/README.md)                     |
| `@effect/sql`                     | SQL database utilities                                                                      | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql/README.md)                     |
| `@effect/sql-clickhouse`          | An `@effect/sql` implementation for [ClickHouse](https://clickhouse.com/).                  | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql-clickhouse/README.md)          |
| `@effect/sql-d1`                  | An `@effect/sql` implementation for [Cloudflare D1](https://developers.cloudflare.com/d1/). | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql-d1/README.md)                  |
| `@effect/sql-drizzle`             | An `@effect/sql` implementation for [Drizzle](https://orm.drizzle.team/).                   | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql-drizzle/README.md)             |
| `@effect/sql-kysely`              | An `@effect/sql` implementation for [Kysely](https://kysely.dev/).                          | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql-kysely/README.md)              |
| `@effect/sql-libsql`              | An `@effect/sql` implementation using the `@libsql/client` library.                         | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql-libsql/README.md)              |
| `@effect/sql-mssql`               | An `@effect/sql` implementation using the mssql `tedious` library.                          | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql-mssql/README.md)               |
| `@effect/sql-mysql2`              | An `@effect/sql` implementation using the `mysql2` library.                                 | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql-mysql2/README.md)              |
| `@effect/sql-pg`                  | An `@effect/sql` implementation using the `postgres.js` library.                            | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql-pg/README.md)                  |
| `@effect/sql-sqlite-bun`          | An `@effect/sql` implementation using the `bun:sqlite` library.                             | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql-sqlite-bun/README.md)          |
| `@effect/sql-sqlite-do`           | An `@effect/sql` implementation for Cloudflare Durable Objects sqlite storage.              | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql-sqlite-do/README.md)           |
| `@effect/sql-sqlite-node`         | An `@effect/sql` implementation using the `better-sqlite3` library.                         | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql-sqlite-node/README.md)         |
| `@effect/sql-sqlite-react-native` | An `@effect/sql` implementation using the `react-native-quick-sqlite` library.              | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql-sqlite-react-native/README.md) |
| `@effect/sql-sqlite-wasm`         | An `@effect/sql` implementation using the `@sqlite.org/sqlite-wasm` library.                | [README](https://github.com/Effect-TS/effect/blob/main/packages/sql-sqlite-wasm/README.md)         |
| `@effect/typeclass`               | Functional programming type classes                                                         | [README](https://github.com/Effect-TS/effect/blob/main/packages/typeclass/README.md)               |
| `@effect/vitest`                  | Testing utilities for [Vitest](https://vitest.dev/)                                         | [README](https://github.com/Effect-TS/effect/blob/main/packages/vitest/README.md)                  |
| `@effect/workflow`                | Durable workflows for Effect                                                                | [README](https://github.com/Effect-TS/effect/blob/main/packages/workflow/README.md)                |

# Documentation

## Website

For detailed information and usage examples, visit the [Effect website](https://www.effect.website/).

## API Reference

For a complete API reference of the core package `effect`, see the [Effect API documentation](https://effect-ts.github.io/effect/).

## Introduction to Effect

Get started with Effect by watching our introductory video on YouTube. This video provides an overview of Effect and its key features:

[![Introduction to Effect](https://img.youtube.com/vi/ViSiXfBKElQ/maxresdefault.jpg)](https://youtu.be/ViSiXfBKElQ)

# Connect with Our Community

Join the Effect community on Discord to connect with other developers, ask questions, and share insights: [Join Effect's Discord Community](https://discord.gg/hdt7t7jpvn).

# Contributing via Pull Requests

We welcome contributions via pull requests! Here are some guidelines to help you get started:

## Setting Up Your Environment

Begin by forking the repository and clone it to your local machine.

Navigate into the cloned repository and create a new branch for your changes:

```bash
git checkout -b my-branch
```

Ensure all required dependencies are installed by running:

```bash
pnpm install  # Requires pnpm version 10.4.0
```

## Making Changes

### Implement Your Changes

Make the changes you propose to the codebase. If your changes impact functionality, please **add corresponding tests** to validate your updates.

### Validate Your Changes

Run the following commands to ensure your changes do not introduce any issues:

- `pnpm codegen` (optional): Re-generate the package entrypoints in case you have changed the structure of a package or introduced a new module.
- `pnpm check`: Confirm that the code compiles without errors.
- `pnpm test`: Execute all unit tests to ensure your changes haven't broken existing functionality.
- `pnpm circular`: Check for any circular dependencies in imports.
- `pnpm lint`: Ensure the code adheres to our coding standards.
  - If you encounter style issues, use `pnpm lint-fix` to automatically correct some of these.
- `pnpm test-types`: Run type-level tests. Tests are written using [tstyche](https://tstyche.org/).
- `pnpm docgen`: Ensure the documentation generates correctly and reflects any changes made.

### Document Your Changes

#### JSDoc Comments

When adding a new feature, it's important to document your code using JSDoc comments. This helps other developers understand the purpose and usage of your changes. Include at least the following in your JSDoc comments:

- **A Short Description**: Summarize the purpose and functionality of the feature.
- **Example**: Provide a usage example under the `@example` tag to demonstrate how to use the feature.
- **Since Version**: Use the `@since` tag to indicate the version in which the feature was introduced. If you're unsure about the version, please consult with a project maintainer.
- **Category (Optional)**: You can categorize the feature with the `@category` tag to help organize the documentation. If you're unsure about what category to assign, ask a project maintainer.

**Note**: A HTML utility file, [`code2jsdoc-example.html`](/scripts/jsdocs/code2jsdoc-example.html), has been added to assist with creating JSDoc `@example` comments. This web-based interface includes two text areas:

1. An input textarea for pasting example code.
2. An output textarea that dynamically generates formatted JSDoc `@example` comments.

This utility helps ensure consistent formatting and streamlines the process of documenting examples. See the following example of its usage:

Example Input:

```ts
import { Effect } from "effect"

console.log(Effect.runSyncExit(Effect.succeed(1)))
/*
Output:
{
  _id: "Exit",
  _tag: "Success",
  value: 1
}
*/
```

Output:

````
*
* @example
* ```ts
* import { Effect } from "effect"
*
* console.log(Effect.runSyncExit(Effect.succeed(1)))
* // Output:
* // {
* //   _id: "Exit",
* //   _tag: "Success",
* //   value: 1
* // }
* ```
*
````

By using this utility, you can save time and maintain consistency in your JSDoc comments, especially for complex examples.

#### Changeset Documentation

Before committing your changes, document them with a changeset. This process helps in tracking modifications and effectively communicating them to the project team and users:

```bash
pnpm changeset
```

During the changeset creation process, you will be prompted to select the appropriate level for your changes:

- **patch**: Opt for this if you are making small fixes or minor changes that do not affect the library's overall functionality.
- **minor**: Choose this for new features that enhance functionality but do not disrupt existing features.
- **major**: Select this for any changes that result in backward-incompatible modifications to the library.

## Finalizing Your Contribution

### Commit Your Changes

Once you have documented your changes with a changeset, it’s time to commit them to the repository. Use a clear and descriptive commit message, which could be the same message you used in your changeset:

```bash
git commit -am 'Add some feature'
```

#### Linking to Issues

If your commit addresses an open issue, reference the issue number directly in your commit message. This helps to link your contribution clearly to specific tasks or bug reports. Additionally, if your commit resolves the issue, you can indicate this by adding a phrase like `", closes #"`. For example:

```bash
git commit -am 'Add some feature, closes #123'
```

This practice not only helps in tracking the progress of issues but also automatically closes the issue when the commit is merged, streamlining project management.

### Push to Your Fork

Push the changes up to your GitHub fork:

```bash
git push origin my-branch
```

### Create a Pull Request

Open a pull request against the appropriate branch on the original repository:

- `main` branch: For minor patches or bug fixes.
- `next-minor` branch: For new features that are non-breaking.
- `next-major` branch: For changes that introduce breaking modifications.

Please be patient! We will do our best to review your pull request as soon as possible.

anthropics/claude-code-action

Sun, 09 Nov 2025 00:04:46 GMT

anthropics/claude-code-action

Language: TypeScript

Stars: 3,988

Forks: 1,219

Stars today: 15 stars today

README

![Claude Code Action responding to a comment](https://github.com/user-attachments/assets/1d60c2e9-82ed-4ee5-b749-f9e021c85f4d)

# Claude Code Action

A general-purpose [Claude Code](https://claude.ai/code) action for GitHub PRs and issues that can answer questions and implement code changes. This action intelligently detects when to activate based on your workflow context—whether responding to @claude mentions, issue assignments, or executing automation tasks with explicit prompts. It supports multiple authentication methods including Anthropic direct API, Amazon Bedrock, and Google Vertex AI.

## Features

- 🎯 **Intelligent Mode Detection**: Automatically selects the appropriate execution mode based on your workflow context—no configuration needed
- 🤖 **Interactive Code Assistant**: Claude can answer questions about code, architecture, and programming
- 🔍 **Code Review**: Analyzes PR changes and suggests improvements
- ✨ **Code Implementation**: Can implement simple fixes, refactoring, and even new features
- 💬 **PR/Issue Integration**: Works seamlessly with GitHub comments and PR reviews
- 🛠️ **Flexible Tool Access**: Access to GitHub APIs and file operations (additional tools can be enabled via configuration)
- 📋 **Progress Tracking**: Visual progress indicators with checkboxes that dynamically update as Claude completes tasks
- 🏃 **Runs on Your Infrastructure**: The action executes entirely on your own GitHub runner (Anthropic API calls go to your chosen provider)
- ⚙️ **Simplified Configuration**: Unified `prompt` and `claude_args` inputs provide clean, powerful configuration aligned with Claude Code SDK

## 📦 Upgrading from v0.x?

**See our [Migration Guide](./docs/migration-guide.md)** for step-by-step instructions on updating your workflows to v1.0. The new version simplifies configuration while maintaining compatibility with most existing setups.

## Quickstart

The easiest way to set up this action is through [Claude Code](https://claude.ai/code) in the terminal. Just open `claude` and run `/install-github-app`.

This command will guide you through setting up the GitHub app and required secrets.

**Note**:

- You must be a repository admin to install the GitHub app and add secrets
- This quickstart method is only available for direct Anthropic API users. For AWS Bedrock or Google Vertex AI setup, see [docs/cloud-providers.md](./docs/cloud-providers.md).

## 📚 Solutions & Use Cases

Looking for specific automation patterns? Check our **[Solutions Guide](./docs/solutions.md)** for complete working examples including:

- **🔍 Automatic PR Code Review** - Full review automation
- **📂 Path-Specific Reviews** - Trigger on critical file changes
- **👥 External Contributor Reviews** - Special handling for new contributors
- **📝 Custom Review Checklists** - Enforce team standards
- **🔄 Scheduled Maintenance** - Automated repository health checks
- **🏷️ Issue Triage & Labeling** - Automatic categorization
- **📖 Documentation Sync** - Keep docs updated with code changes
- **🔒 Security-Focused Reviews** - OWASP-aligned security analysis
- **📊 DIY Progress Tracking** - Create tracking comments in automation mode

Each solution includes complete working examples, configuration details, and expected outcomes.

## Documentation

- **[Solutions Guide](./docs/solutions.md)** - **🎯 Ready-to-use automation patterns**
- **[Migration Guide](./docs/migration-guide.md)** - **⭐ Upgrading from v0.x to v1.0**
- [Setup Guide](./docs/setup.md) - Manual setup, custom GitHub apps, and security best practices
- [Usage Guide](./docs/usage.md) - Basic usage, workflow configuration, and input parameters
- [Custom Automations](./docs/custom-automations.md) - Examples of automated workflows and custom prompts
- [Configuration](./docs/configuration.md) - MCP servers, permissions, environment variables, and advanced settings
- [Experimental Features](./docs/experimental.md) - Execution modes and network restrictions
- [Cloud Providers](./docs/cloud-providers.md) - AWS Bedrock and Google Vertex AI setup
- [Capabilities & Limitations](./docs/capabilities-and-limitations.md) - What Claude can and cannot do
- [Security](./docs/security.md) - Access control, permissions, and commit signing
- [FAQ](./docs/faq.md) - Common questions and troubleshooting

## 📚 FAQ

Having issues or questions? Check out our [Frequently Asked Questions](./docs/faq.md) for solutions to common problems and detailed explanations of Claude's capabilities and limitations.

## License

This project is licensed under the MIT License—see the LICENSE file for details.

calcom/cal.com

Sun, 09 Nov 2025 00:04:45 GMT

calcom/cal.com

Scheduling infrastructure for absolutely everyone.

Language: TypeScript

Stars: 38,715

Forks: 10,986

Stars today: 15 stars today

README

Cal.com

The open-source Calendly successor.
Learn more »

Discussions · Website · Issues · Roadmap

## About the Project # Scheduling infrastructure for absolutely everyone The open source Calendly successor. You are in charge of your own data, workflow, and appearance. Calendly and other scheduling tools are awesome. It made our lives massively easier. We're using it for business meetings, seminars, yoga classes, and even calls with our families. However, most tools are very limited in terms of control and customization. That's where Cal.com comes in. Self-hosted or hosted by us. White-label by design. API-driven and ready to be deployed on your own domain. Full control of your events and data. ## Recognition #### [Hacker News](https://news.ycombinator.com/from?site=cal.com) #### [Product Hunt](https://producthunt.com/products/cal-com?utm_source=badge-top-post-badge&utm_medium=badge) This project is tested with browserstack ### Built With - [Next.js](https://nextjs.org/?ref=cal.com) - [tRPC](https://trpc.io/?ref=cal.com) - [React.js](https://reactjs.org/?ref=cal.com) - [Tailwind CSS](https://tailwindcss.com/?ref=cal.com) - [Prisma.io](https://prisma.io/?ref=cal.com) - [Daily.co](https://go.cal.com/daily) ## Contact us Meet our sales team for any commercial inquiries. ## Stay Up-to-Date Cal.com officially launched as v.1.0 on the 15th of September 2021 and we've come a long way so far. Watch **releases** of this repository to be notified of future updates: ![cal-star-github](https://user-images.githubusercontent.com/8019099/154853944-a9e3c999-3da3-4048-b149-b4f73893c6fb.gif) ## Getting Started To get a local copy up and running, please follow these simple steps. ### Prerequisites Here is what you need to be able to run Cal.com. - Node.js (Version: >=18.x) - PostgreSQL (Version: >=13.x) - Yarn _(recommended)_ > If you want to enable any of the available integrations, you may want to obtain additional credentials for each one. More details on this can be found below under the [integrations section](#integrations). ## Development ### Setup 1. Clone the repo into a public GitHub repository (or fork https://github.com/calcom/cal.com/fork). If you plan to distribute the code, keep the source code public to comply with [AGPLv3](https://github.com/calcom/cal.com/blob/main/LICENSE). To clone in a private repository, [acquire a commercial license](https://cal.com/sales) ```sh git clone https://github.com/calcom/cal.com.git ``` > If you are on Windows, run the following command on `gitbash` with admin privileges:
> `git clone -c core.symlinks=true https://github.com/calcom/cal.com.git`
> See [docs](https://cal.com/docs/how-to-guides/how-to-troubleshoot-symbolic-link-issues-on-windows#enable-symbolic-links) for more details. 2. Go to the project folder ```sh cd cal.com ``` 3. Install packages with yarn ```sh yarn ``` 4. Set up your `.env` file - Duplicate `.env.example` to `.env` - Use `openssl rand -base64 32` to generate a key and add it under `NEXTAUTH_SECRET` in the `.env` file. - Use `openssl rand -base64 32` to generate a key and add it under `CALENDSO_ENCRYPTION_KEY` in the `.env` file. 5. Setup Node If your Node version does not meet the project's requirements as instructed by the docs, "nvm" (Node Version Manager) allows using Node at the version required by the project: ```sh nvm use ``` You first might need to install the specific version and then use it: ```sh nvm install && nvm use ``` You can install nvm from [here](https://github.com/nvm-sh/nvm). #### Quick start with `yarn dx` > - **Requires Docker and Docker Compose to be installed** > - Will start a local Postgres instance with a few test users - the credentials will be logged in the console ```sh yarn dx ``` #### Development tip 1. Add `export NODE_OPTIONS=“--max-old-space-size=16384”` to your shell script to increase the memory limit for the node process. Alternatively, you can run this in your terminal before running the app. Replace 16384 with the amount of RAM you want to allocate to the node process. 2. Add `NEXT_PUBLIC_LOGGER_LEVEL={level}` to your .env file to control the logging verbosity for all tRPC queries and mutations.\ Where {level} can be one of the following: `0` for silly \ `1` for trace \ `2` for debug \ `3` for info \ `4` for warn \ `5` for error \ `6` for fatal When you set `NEXT_PUBLIC_LOGGER_LEVEL={level}` in your .env file, it enables logging at that level and higher. Here's how it works: The logger will include all logs that are at the specified level or higher. For example: \ - If you set `NEXT_PUBLIC_LOGGER_LEVEL=2`, it will log from level 2 (debug) upwards, meaning levels 2 (debug), 3 (info), 4 (warn), 5 (error), and (fatal) will be logged. \ - If you set `NEXT_PUBLIC_LOGGER_LEVEL=3`, it will log from level 3 (info) upwards, meaning levels 3 (info), 4 (warn), 5 (error), and 6 (fatal) will be logged, but level 2 (debug) and level 1 (trace) will be ignored. \ ```sh echo 'NEXT_PUBLIC_LOGGER_LEVEL=3' >> .env ``` for Logger level to be set at info, for example. #### Gitpod Setup 1. Click the button below to open this project in Gitpod. 2. This will open a fully configured workspace in your browser with all the necessary dependencies already installed. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/calcom/cal.com) #### Manual setup 1. Configure environment variables in the `.env` file. Replace ``, ``, ``, and `` with their applicable values ``` DATABASE_URL='postgresql://:@:' ```

If you don't know how to configure the DATABASE_URL, then follow the steps here to create a quick local DB

1. [Download](https://www.postgresql.org/download/) and install postgres in your local (if you don't have it already). 2. Create your own local db by executing `createDB ` 3. Now open your psql shell with the DB you created: `psql -h localhost -U postgres -d ` 4. Inside the psql shell execute `\conninfo`. And you will get the following info. ![image](https://user-images.githubusercontent.com/39329182/236612291-51d87f69-6dc1-4a23-bf4d-1ca1754e0a35.png) 5. Now extract all the info and add it to your DATABASE_URL. The url would look something like this `postgresql://postgres:postgres@localhost:5432/Your-DB-Name`. The port is configurable and does not have to be 5432.

If you don't want to create a local DB. Then you can also consider using services like railway.app, Northflank or render. - [Setup postgres DB with railway.app](https://docs.railway.app/guides/postgresql) - [Setup postgres DB with Northflank](https://northflank.com/guides/deploy-postgres-database-on-northflank) - [Setup postgres DB with render](https://render.com/docs/databases) 1. Copy and paste your `DATABASE_URL` from `.env` to `.env.appStore`. 1. Set up the database using the Prisma schema (found in `packages/prisma/schema.prisma`) In a development environment, run: ```sh yarn workspace @calcom/prisma db-migrate ``` In a production environment, run: ```sh yarn workspace @calcom/prisma db-deploy ``` 1. Run [mailhog](https://github.com/mailhog/MailHog) to view emails sent during development > **_NOTE:_** Required when `E2E_TEST_MAILHOG_ENABLED` is "1" ```sh docker pull mailhog/mailhog docker run -d -p 8025:8025 -p 1025:1025 mailhog/mailhog ``` 1. Run (in development mode) ```sh yarn dev ``` #### Setting up your first user ##### Approach 1 1. Open [Prisma Studio](https://prisma.io/studio) to look at or modify the database content: ```sh yarn db-studio ``` 1. Click on the `User` model to add a new user record. 1. Fill out the fields `email`, `username`, `password`, and set `metadata` to empty `{}` (remembering to encrypt your password with [BCrypt](https://bcrypt-generator.com/)) and click `Save 1 Record` to create your first user. > New users are set on a `TRIAL` plan by default. You might want to adjust this behavior to your needs in the `packages/prisma/schema.prisma` file. 1. Open a browser to [http://localhost:3000](http://localhost:3000) and login with your just created, first user. ##### Approach 2 Seed the local db by running ```sh cd packages/prisma yarn db-seed ``` The above command will populate the local db with dummy users. ### E2E-Testing Be sure to set the environment variable `NEXTAUTH_URL` to the correct value. If you are running locally, as the documentation within `.env.example` mentions, the value should be `http://localhost:3000`. ```sh # In a terminal just run: yarn test-e2e # To open the last HTML report run: yarn playwright show-report test-results/reports/playwright-html-report ``` #### Resolving issues ##### E2E test browsers not installed Run `npx playwright install` to download test browsers and resolve the error below when running `yarn test-e2e`: ``` Executable doesn't exist at /Users/alice/Library/Caches/ms-playwright/chromium-1048/chrome-mac/Chromium.app/Contents/MacOS/Chromium ``` ### Upgrading from earlier versions 1. Pull the current version: ```sh git pull ``` 1. Check if dependencies got added/updated/removed ```sh yarn ``` 1. Apply database migrations by running one of the following commands: In a development environment, run: ```sh yarn workspace @calcom/prisma db-migrate ``` (This can clear your development database in some cases) In a production environment, run: ```sh yarn workspace @calcom/prisma db-deploy ``` 1. Check for `.env` variables changes ```sh yarn predev ``` 1. Start the server. In a development environment, just do: ```sh yarn dev ``` For a production build, run for example: ```sh yarn build yarn start ``` 1. Enjoy the new version. ## Deployment ### Docker **Official support**: Our team will begin to officially support the Dockerfile and docker-compose resources in this repository. **Important**: Cal.com will **not** be supporting installations that use these Docker resources. While we provide and maintain the Docker configurations, support for Docker-based installations is the responsibility of the user. This image can be found on DockerHub at [https://hub.docker.com/r/calcom/cal.com](https://hub.docker.com/r/calcom/cal.com). **Note for ARM Users**: Use the {version}-arm suffix for pulling images. Example: `docker pull calcom/cal.com:v5.6.19-arm`. #### Requirements Make sure you have `docker` & `docker compose` installed on the server / system. Both are installed by most docker utilities, including Docker Desktop and Rancher Desktop. Note: `docker compose` without the hyphen is now the primary method of using docker-compose, per the Docker documentation. #### (Most users) Running Cal.com with Docker Compose If you are evaluating Cal.com or running with minimal to no modifications, this option is for you. 1. Clone calcom/cal.com ```bash git clone --recursive https://github.com/calcom/cal.com.git ``` 2. Change into the directory ```bash cd cal.com ``` 3. Prepare your configuration: Rename `.env.example` to `.env` and then update `.env` ```bash cp .env.example .env ``` Most configurations can be left as-is, but for configuration options see [Important Run-time variables](#important-run-time-variables) below. **Push Notifications (VAPID Keys)** If you see an error like: ``` Error: No key set vapidDetails.publicKey ``` This means your environment variables for Web Push are missing. You must generate and set `NEXT_PUBLIC_VAPID_PUBLIC_KEY` and `VAPID_PRIVATE_KEY`. Generate them with: ```bash npx web-push generate-vapid-keys ``` Then update your `.env` file: ```env NEXT_PUBLIC_VAPID_PUBLIC_KEY=your_public_key_here VAPID_PRIVATE_KEY=your_private_key_here ``` Do **not** commit real keys to `.env.example` — only placeholders. Update the appropriate values in your .env file, then proceed. 4. (optional) Pre-Pull the images by running the following command: ```bash docker compose pull ``` This will use the default image locations as specified by `image:` in the docker-compose.yaml file. Note: To aid with support, by default Scarf.sh is used as registry proxy for download metrics. 5. Start Cal.com via docker compose (Most basic users, and for First Run) To run the complete stack, which includes a local Postgres database, Cal.com web app, and Prisma Studio: ```bash docker compose up -d ``` To run Cal.com web app and Prisma Studio against a remote database, ensure that DATABASE_URL is configured for an available database and run: ```bash docker compose up -d calcom studio ``` To run only the Cal.com web app, ensure that DATABASE_URL is configured for an available database and run: ```bash docker compose up -d calcom ``` **Note: to run in attached mode for debugging, remove `-d` from your desired run command.** 6. Open a browser to [http://localhost:3000](http://localhost:3000), or your defined NEXT_PUBLIC_WEBAPP_URL. The first time you run Cal.com, a setup wizard will initialize. Define your first user, and you're ready to go! #### Updating Cal.com 1. Stop the Cal.com stack ```bash docker compose down ``` 2. Pull the latest changes ```bash docker compose pull ``` 3. Update env vars as necessary. 4. Re-start the Cal.com stack ```bash docker compose up -d ``` #### (Advanced users) Build and Run Cal.com 1. Clone calcom/docker. ```bash git clone https://github.com/calcom/cal.com.git calcom-docker ``` 2. Change into the directory ```bash cd calcom-docker ``` 3. Update the calcom submodule. This project depends on the Cal.com source code, which is included here as a Git submodule. To make sure you get everything you need, update the submodule with the command below. ```bash git submodule update --remote --init ``` Note: DO NOT use recursive submodule update, otherwise you will receive a git authentication error. 4. Rename `.env.example` to `.env` and then update `.env` For configuration options see [Build-time variables](#build-time-variables) below. Update the appropriate values in your .env file, then proceed. 5. Build the Cal.com docker image: Note: Due to application configuration requirements, an available database is currently required during the build process. a) If hosting elsewhere, configure the `D ... [README content truncated due to size. Visit the repository for the complete README] ...

GitHub Trending Today for typescript - TypeScript Daily

umami-software/umami

README

Umami

nocobase/nocobase

README

ad-on-is/rachoon

README

langfuse/langfuse

README

Langfuse Is Doubling Down On Open Source Langfuse Cloud · Self Host · Demo

angular/angular

README

Angular - The modern web developer's platform

actions/starter-workflows

README

simstudioai/sim

README

open-metadata/OpenMetadata

README

NginxProxyManager/nginx-proxy-manager

README

blakeblackshear/frigate

README

FlowiseAI/Flowise

README

Build AI Agents, Visually

continuedev/continue

README

Continue

humanlayer/humanlayer

README

[Join Waitlist](https://humanlayer.dev/code) | [Discord](https://humanlayer.dev/discord)

better-auth/better-auth

README

Better Auth

farion1231/cc-switch

README

backstage/backstage

README

Effect-TS/effect

README

anthropics/claude-code-action

README

calcom/cal.com

README

Cal.com

Langfuse Is Doubling Down On Open Source

Langfuse Cloud · Self Host · Demo