dyrector.io
  • Welcome 👋
  • Basics
    • Who is it for?
    • How it works
    • Components
    • Use cases
    • API
  • Tutorials
    • Getting started
    • Add your Node
    • Add your Registry
      • Add V2 Registry
      • Add Docker Hub Registry
      • Add GitHub Registry
      • Add GitLab Registry
      • Add Google Registry
      • Add Unchecked Registry
    • Create your Project
      • Create a versionless project
      • Create a versioned project
        • Create a Rolling Version
        • Create an Incremental Version
        • Add a version to your Versioned Project
    • Deploy your Project
    • Create Chat Notifications
    • Inject Files to a Container
  • Features
    • Core functionality
    • Templates
      • Vaultwarden
      • Strapi
      • Cal.com
      • WordPress
      • Minecraft Server
      • Google Microservices Demo
      • Self-managed GitLab
      • MLflow
      • Gitea
      • LinkAce
    • Continuous Deployment
    • Configuration management
      • Container configuration
      • Configuration bundle
    • Monitoring
    • Audit log
    • Storage
  • Self-managed
    • Quick start
    • CLI
    • Proxies
    • Environment variables
    • Self-signed certificates
  • Learn more
    • Changelog
    • Quality Assurance (QA)
    • Roadmap
      • Features in progress
      • Integrations in progress
    • Pricing
    • FAQ
      • Portainer vs. dyrector.io
    • Community
Powered by GitBook
On this page
  • Why use dyrector.io to set up Cal.com
  • Set up Cal.com
Edit on GitHub
Export as PDF
  1. Features
  2. Templates

Cal.com

Last updated 2 years ago

Cal.com is a meeting scheduler application. Users can set up its self-hosted stack.

Why use dyrector.io to set up Cal.com

Cal.com is awesome. We like it and use it everyday, people like it, too. Chances are, if you're here, you like it, as well. Even better that they provide self-hosted usage. But as some users pointed out on , self-hosting Cal.com is a challenging process. So, we turned it into a template for easy setup.

Set up Cal.com

After the Node where you'd like to run Cal.com is , you can set it up by following the steps of deployments as documented .

Configuration

  • cal-db (latest)

    • POSTGRES_PASSWORD has to be specified.

  • cal-com (2.5.10)

    • DATABASE_URL needs to contain POSTGRES_PASSWORD's value in postgresql://cal-user:${POSTGRES_PASSWORD}@cal-db:5432/cal-db for cal-db.

    • NEXTAUTH_SECRET and CALENDSO_ENCRYPTION_KEY needs to be specified. We recommend to generate these secrets.

    • If you have a node with Traefik enabled you can use http://cal.localhost (or any other domain setup in the ingress settings) by setting NEXT_PUBLIC_WEBAPP_URL to the public URL.

Once the deployment is successful, self-hosted Cal.com is ready to use at by default, as seen below.

Hacker News
registered
here
OpenSSL
localhost:7000