Skip to content
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.

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

"NEXT_PUBLIC_E2E_TEST" is not recognized as internal or external command #182

Closed
Jorgelig opened this issue Dec 12, 2022 · 3 comments · Fixed by #184
Closed

"NEXT_PUBLIC_E2E_TEST" is not recognized as internal or external command #182

Jorgelig opened this issue Dec 12, 2022 · 3 comments · Fixed by #184

Comments

@Jorgelig
Copy link
Contributor

After installing the dependencies and copying the .env files, in windows 10, with docker I get the error: "NEXT_PUBLIC_E2E_TEST" is not recognized as internal or external command. I looked for information in the configuration pages and I did not find what I should put as a value in the .env file for that variable or what dependency I would need to install

@baptisteArno
Copy link
Owner

Can you tell me what instructions you have followed?

@Jorgelig
Copy link
Contributor Author

Jorgelig commented Dec 12, 2022

  1. Clone the repo
  2. Install dependencies
  3. Set up environment variables
Copy apps/builder/.env.local.example to apps/builder/.env.local
Copy apps/viewer/.env.local.example to apps/viewer/.env.local
Copy packages/db/.env.example to packages/db/.env
  1. Start the builder and viewer
pnpm dev

image

ñññ

@Jorgelig
Copy link
Contributor Author

I already managed to make it compatible with windows 10, adapt the dev script:

"dev": "pnpm docker:up && cross-env NEXT_PUBLIC_E2E_TEST=false && turbo run dev --filter=builder... --filter=viewer... --parallel --no-cache",

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants