-
Notifications
You must be signed in to change notification settings - Fork 80
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
Docker deployment map is gray #983
Comments
Hi @brodyFlannigan, thanks for reporting this! We'll take a look and get back to you shortly |
Thanks for reporting! We'll be able to patch this soon. As a stopgap fix, you can open We'll put out a patch that removes this unhelpful configuration line. |
The removal of line 5 (Optional map tile URL) did the trick! Thanks! I'll leave the issue open as I understand you're working on a more long-term solution :) |
I did remove line 5 but it did not work. My map stays grey. Did you setup a more permanent fix ? Thanks ! |
Does your network inspector show any failed requests? If so, could you please share a screenshot? |
Nope. No failed requests. There seems to be no requests made to mapbox... |
We found a fix for this! Please add |
Observed behavior (please include a screenshot if possible)
When using the docker quickstart (which is amazing, by the way) The map is simply gray, without any map background. Stop locations are visible but there's nothing behind them. This is an issue even with a mapbox key set in the configuration. Looking at the network tab, I'm seeing requests being made to
http://localhost:9966/feed/40a70eaf-9bc1-402b-9867-604a479d12b5/optional-map-tile-url
when I move the map around, which doesn't seem to be normal.Expected behavior
Map should have background
Steps to reproduce the problem
6fc72d2148e8dda005aae9c2b26ba911e4197506
docker-compose up
as suggested in README.Any special notes on configuration used
Nothing special other than changing my mapbox key in /configurations/default/env.yml
Version of datatools-ui and datatools-server if applicable (exact commit hash or branch name)
Commit
6fc72d2148e8dda005aae9c2b26ba911e4197506
The text was updated successfully, but these errors were encountered: