You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
+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?
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:
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 PRThe text was updated successfully, but these errors were encountered: