-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Two separate bugfixes. #1120
Two separate bugfixes. #1120
Conversation
NegatioN
commented
May 26, 2016
- Bugfix goToTrace not triggering on other pages than default, creating a malformed url.
- webpack devproxy only targeted default-page locally, and got resources from upstream api if you attached an external dev-server. The external zipkin-server can now be configured with an environment-variable.
1. Bugfix goToTrace not triggering on other pages than default, creating a malformed url. 2. webpack devproxy only targeted default-page locally, and got resources from upstream api if you attached an external dev-server. The external zipkin-server can now be configured with an environment-variable.
thanks! mind putting in the README how to connect to an existing zipkin server (ex via docker or some other specified ip)? |
I'm not sure if this is exactly what you were looking for. Please give me a shout if it wasn't. :) |
Thanks! |
Heh. Ran into this today when I tried to modify the UI, if only if I had seen it before my flight... |
What one can synchronise before a flight is indeed important!
|
Flight attendants should remind people to git pull as part of the preflight instructions... |
nice once :)
|
* Two separate bugfixes. 1. Bugfix goToTrace not triggering on other pages than default, creating a malformed url. 2. webpack devproxy only targeted default-page locally, and got resources from upstream api if you attached an external dev-server. The external zipkin-server can now be configured with an environment-variable. * update readme with proxy backend-info