-
Notifications
You must be signed in to change notification settings - Fork 62
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
Environment variable not being set correctly #1056
Comments
Ah that would be annoying, how do you set the environment variable? Do you pass it in docker-compose or do you build the image yourself using this variable? |
And thanks for looking at the existing issue, troubleshooting and testing it on multiple releases btw! |
Thanks for the quick response! I'm setting it in docker-compose, like this:
No worries, I know how much easier troubleshooting is when you as much info as possible! Let me know if there are any other settings that'd help troubleshoot or anything you'd like me to try to test :) |
I tried it and for me it does work when I run this: sudo docker run -e NEXT_PUBLIC_API_BASE_URL=http://localhost:3400 -p 3000:3000 --name frontend ghcr.io/evroon/bracket-frontend:v2.0.1 Then you can remove that container and try again with a new port sudo docker rm -f frontend
sudo docker run -e NEXT_PUBLIC_API_BASE_URL=http://localhost:6800 -p 3000:3000 --name frontend ghcr.io/evroon/bracket-frontend:v2.0.1 And then if you press CTRL + F5 in the browser (or disable caching), you should see that it now uses It didn't work for me a while until I figured out F5 keeps that old port in the memory cache because it caches the file that looks like @dickravison Could you let me know if this solves the issue for you? |
Hi @evroon, thanks for creating this, it's great! I'm having an issue when updating from v1.5.3 to v2.0.0+. I get this error:
This is only when using a public endpoint instead of localhost. I have set
NEXT_PUBLIC_API_BASE_URL
to my public endpoint and this works fine on v1.5.3 but not on v2.0.0+. It looks as though this env var isn't being set for some reason. Could the bug detailed in this issue have come back?#843
I've tested this on v2.0.0, v2.0.1 and v2.0.2 and all of them have the same issue. Let me know if you need any more info.
The text was updated successfully, but these errors were encountered: