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.

Sign up for GitHub

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

Jump to bottom

document packaging #15

Open

codefromthecrypt opened this issue Mar 30, 2016 · 1 comment

Member

codefromthecrypt commented Mar 30, 2016

there's no more need for zipkin-web, it is probably helpful to relate how it is that the zipkin-server ends up with web assets.

the api and ui are often cohosted on the same process, but for example, the javascript assets (zipkin-ui) could be hosted on nginx.

there are two options for the cohosted process, scala or java

scala - the -all jar here: https://jcenter.bintray.com/io/zipkin/zipkin-query-service/1.39.0/
- includes http transport, mysql and cassandra storage, and zipkin-ui
java - the -exec jar here: https://jcenter.bintray.com/io/zipkin/java/zipkin-server/0.10.0/
- includes http and kafka transports, elasticsearch, mysql and cassandra storage, and zipkin-ui

technically, both of these have javascript assets because they bundle zipkin-ui and know how to serve it https://jcenter.bintray.com/io/zipkin/zipkin-ui/1.39.0/

hopefully, one day we'll only have one option to document :) openzipkin/zipkin#1071

codefromthecrypt mentioned this issue

Final edits #14

Merged

Member Author

codefromthecrypt commented Mar 30, 2016

See openzipkin/zipkin#1074 for possible drift in the jar name of the scala zipkin-query-service

abesto pushed a commit that referenced this issue


          Update quickstart with Apache coordinates (#15)

52d9176

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment