fix: add root .env.example referenced by README setup#3
Open
khakimio wants to merge 1 commit into
Open
Conversation
The README setup step runs `cp .env.example .env` from the repo root, but no root .env.example existed (only per-app ones under apps/api and apps/web), so the command failed with "No such file or directory". Add a root .env.example mirroring apps/api/.env.example — these are the server keys the README env table documents. The web app keeps its own apps/web/.env.example since Next.js reads .env from its own directory. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@khakimio is attempting to deploy a commit to the Midday Labs AB Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README setup step runs
cp .env.example .envfrom the repo root, but no root .env.example existed (only per-app ones under apps/api and apps/web), so the command failed with "No such file or directory".Add a root .env.example mirroring apps/api/.env.example — these are the server keys the README env table documents. The web app keeps its own apps/web/.env.example since Next.js reads .env from its own directory.