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.

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

Jump to bottom

Parameters missing in docker/k8s environment [PR] #636

Open
fashberg opened this issue Oct 16, 2022 · 1 comment · May be fixed by #637
Open

Parameters missing in docker/k8s environment [PR] #636

fashberg opened this issue Oct 16, 2022 · 1 comment · May be fixed by #637

Comments

@fashberg
Copy link
Contributor

Hey!

I'm running kutt in k8s with helm deployment (using original kutt/kutt).
There are all parameters set via ENV-Variabbles missing in client, e.g. DEFAULT_DOMAIN is empty.

How to test if's wrong:

  • all-pages: There is only the icon, no site-name
  • /terms : no url in text
  • domain-dropdown has empty entry

fix

after some search:
next.config.js is using require("dotenv").config(); - but there is no .env inside the container!
The .env is outside the container when using docker-compose. Documentation says nothing about this.

I've added an entrypoint.sh which creates an .env-file from the ENV-Variables . see PR
@fashberg fashberg linked a pull request Oct 16, 2022 that will close this issue
Open
@dkyeremeh dkyeremeh mentioned this issue Dec 7, 2022
Open
@mind-overflow
Copy link

+1 on this, it's pretty important imho, especially since i'm guessing that the JWT token is also not ported inside of the container and thus the default one is used?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

create-.env-from-env - fixes #636 fashberg/kutt
2 participants
@fashberg @mind-overflow