-
-
Notifications
You must be signed in to change notification settings - Fork 292
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
API Subdomain breaks docker images #10
Comments
Thanks for the heads-up @encima. Just so I understand, do you have trouble if you visit
If you know the IP address that grist will ultimately be served on, you can set some environment variables to let it know. Would this work for you?:
I agree it'd be better if this worked straight out of the box, without the |
I did find the environment variables so that part was ok. but just running with local host causes an issue because connection string tries api.localhost and fails. also, when I set the IP under APP_HOME etc then the api will then try api.168.1.2 instead of api.$IP. Both would fail but I guess the regex is just splitting at the first "."? |
Would it be possible to describe exactly how you are running Grist? Then I could help suggest environment variable changes that might help you. Variables that may be relevant include |
Sorry for the delay here! I did switch to paying for an account with your hosted version but would still like a mirrored, self hosted version. Currently, I am deploying all in a single container with a Lets Encrypt proxy pointing to the grist domain I tested running on my local machine and all works fine so I assume it is something with the proxy (or Caprovers port mapping); I will close now and update if I do succeed in running it this way. |
Currently, the docker instructions do not match the latest version of the code (unless you have a host set up)
gristUrls has a default subdomain of 'api' which, when run with docker, will prepend
api
with the IP of the host.i.e.
![image](https://user-images.githubusercontent.com/517923/111898610-7cf94280-8a27-11eb-877d-00bcfdeefc54.png)
Could we use the
api
route by default instead and make this configurable through an environment variable, perhaps?The text was updated successfully, but these errors were encountered: