Skip to content

docs: document Windows setup fix for prisma .env symlink error #28101

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sahitya-chandra merged 5 commits into from
Mar 1, 2026
+7 −0
Merged

docs: document Windows setup fix for prisma .env symlink error #28101

Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9d6cdf9
docs: add Windows fix for prisma .env symlink issue
khushal-winner Feb 20, 2026
2f3e3d6
Remove 'link-as-an-app' from redirect apps list
khushal-winner Feb 20, 2026
850d685
Update README.md
khushal-winner Mar 1, 2026
c0eda3f
Update README.md
sahitya-chandra Mar 1, 2026
24f3a87
Update README.md
sahitya-chandra Mar 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,6 +150,19 @@ Here is what you need to be able to run Cal.com.
- Use `openssl rand -base64 32` to generate a key and add it under `NEXTAUTH_SECRET` in the `.env` file.
- Use `openssl rand -base64 24` to generate a key and add it under `CALENDSO_ENCRYPTION_KEY` in the `.env` file.

**Windows users**: After setting up your `.env` file, you may encounter an issue with `packages/prisma/.env` being a symlink that fails with "unexpected character / in variable name". This happens because Windows doesn't handle Unix-style symlinks properly.

**Option 1: Use commands** (if you have Git Bash or WSL):
```sh
rm packages/prisma/.env
cp .env packages/prisma/.env
```

**Option 2: Do this manually**:
1. Delete the file `packages/prisma/.env` (it's actually a symlink)
2. Copy your `.env` file from the root directory
3. Paste it into the `packages/prisma/` folder

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:

Expand Down
Loading