Skip to content

docs: add env variable checklist and Windows symlink guidance to README setup#28667

Open
shockzinfinity wants to merge 3 commits intocalcom:mainfrom
shockzinfinity:docs/readme-env-setup-guide
Open

docs: add env variable checklist and Windows symlink guidance to README setup#28667
shockzinfinity wants to merge 3 commits intocalcom:mainfrom
shockzinfinity:docs/readme-env-setup-guide

Conversation

@shockzinfinity
Copy link
Copy Markdown
Contributor

Summary

Expands Step 4 of the README installation guide (.env setup) to help users avoid the most common misconfiguration issues when self-hosting Cal.com.

Changes

Environment variable quick-reference table added after the existing NEXTAUTH_SECRET / CALENDSO_ENCRYPTION_KEY generation commands:

Variable Purpose
NEXTAUTH_SECRET Always required — generate with openssl
CALENDSO_ENCRYPTION_KEY Always required — generate with openssl
DATABASE_URL Change when using a custom/remote database
NEXT_PUBLIC_WEBAPP_URL Must change for any non-localhost deployment
NEXTAUTH_URL Production deployments (leave empty on Vercel)
EMAIL_FROM Custom sender address for outgoing emails

A callout note explicitly links NEXT_PUBLIC_WEBAPP_URL / NEXTAUTH_URL misconfiguration to the well-known localhost redirect issue.

Windows symlink guidance expanded to cover the case where the repository was cloned without admin privileges (the symlink at packages/prisma/.env would not have been created), with the correct git clone -c core.symlinks=true command and a reference link.

Motivation

These are among the most frequently reported self-hosting issues:

The changes are purely documentation — no code is modified.

Allow edits from maintainers ✅

…ME setup

Expand Step 4 of the installation guide to help users avoid the most
common self-hosting misconfiguration issues:

- Add a quick-reference table of key environment variables that must be
  reviewed before starting the app, with notes on when each needs to
  change (NEXTAUTH_SECRET, CALENDSO_ENCRYPTION_KEY, DATABASE_URL,
  NEXT_PUBLIC_WEBAPP_URL, NEXTAUTH_URL, EMAIL_FROM)
- Add a callout note linking NEXT_PUBLIC_WEBAPP_URL / NEXTAUTH_URL
  misconfiguration to the common localhost redirect issue
- Expand Windows symlink guidance to cover the case where admin
  privileges were missing at clone time, with the correct git clone
  command and a link to the Git for Windows symlinks docs

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


shockzM1 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

Removed reference to Git for Windows symlinks from README.
| `EMAIL_FROM` | When you want outgoing emails to show a custom sender address | `Cal.com <noreply@yourdomain.com>` |

> **Note:** Failing to update `NEXT_PUBLIC_WEBAPP_URL` and `NEXTAUTH_URL` is the most common cause of redirect-to-localhost issues after deployment.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we don't need this part in the docs, can you revert them

Copy link
Copy Markdown
Member

@sahitya-chandra sahitya-chandra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this PR does not fixes the linked issue so can you unlink it
and then update the title also. thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants