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

problem with .env file #92

Open
ArtyomCZ opened this issue Jun 1, 2024 · 0 comments
Open

problem with .env file #92

ArtyomCZ opened this issue Jun 1, 2024 · 0 comments

Comments

@ArtyomCZ
Copy link

ArtyomCZ commented Jun 1, 2024

Describe the bug
I created an .env file and defined PUBLIC_KENER_FOLDER and GH_TOKEN. But it seems it is not read when npm run build so I can't run Kener in production mode. Dev mode works fine but without environment variables.

To Reproduce
Steps to reproduce the behavior:

  1. Create fork of Kener repository
  2. Create .env file with variables
  3. npm i
  4. mv config/site.example.yaml config/site.yaml
  5. mv config/monitors.example.yaml config/monitors.yaml
  6. npm run build

Expected behavior
I don't know if I'm missing something, but I assume this should work.

Screenshots
image

Desktop (please complete the following information):

  • OS: MacOS Sonoma
  • IDE: Jetbrains Webstorm
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant