building/running kythe's web UI

[Christian]

Hello,

It is mentioned in the docs that running the web UI now requires to build it from

source, which I am willing to do, but it's a little bit unclear what needs to be built and ran.

Could you clarify those steps?

So far I have been able to bazel build //kythe/web/ui:prod-js , which does provide a

main.js under bazel-bin/kythe/web/ui/resources/public/js/main.js but there is no HTML files

so I'm unclear what shall be passed to

kythe/tools/http_server --public_resources bazel-bin/kythe/web/ui/resources/public

I feel like I'm 99% on the way there but I can't find index.html, probably just missed a step?

Best,

[Shahms King]

I don't believe anyone has on the team built/run the web UI in a good long while. It's certainly likely the documentation is out of date or incomplete but it's hard to say.

My recommendation if you want a UI for navigating Kythe data would be to look into Underhood at https://github.com/TreeTide/underhood

--Shahms

--
You received this message because you are subscribed to the Google Groups "Kythe" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kythe+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kythe/CAEffniaiaBRVjUcUVYb25bC7YzvL6jh%2BV7eLk3WOpPbOVA5T_Q%40mail.gmail.com.

--

:-P

[Robin Palotai]

Hey guys,

I merged back some underhood UI changes some weeks ago that also broke the interface between the kythe gateway and the UI (for sake of the more simple Zoekt backend, see the docker compose demo).

But I don't think it is anything unfixable. If you are interested in the usecase, happy to assist with pointers/review.

BR

Robin

To view this discussion on the web visit https://groups.google.com/d/msgid/kythe/CANeWHAh4dHpPzZ6JkBaHov04UtQK6d67MEu_ROrrOgN5_me8BQ%40mail.gmail.com.

[peter.l...@gmail.com]

I also have a UI that displays a different set of information than Robin's -- it attempts to show all the facts and links for each source item. If anyone is interested, I'll post details. It's designed for Python, but should be able to handle other languages.

[Christian]

Circling back here, in case someone stumbles into this, I was finally able to get the UI running:

build the http_server:

bazel build //kythe/go/serving/tools/http_server

build the UI (leiningen requires java 8):

JAVA_HOME=/opt/java8 bazel build //kythe/web/ui

And then I had to manually copy the static resources:

cp -rv kythe/web/ui/resources/public/* bazel-bin/kythe/web/ui/resources/public

Then I could successfully serve the UI from that directory:

bazel-bin/kythe/go/serving/tools/http_server/http_server --public_resources bazel-bin/kythe/web/ui/resources/public  --listen localhost:8080 --serving_table path/to/kythe_serving

This is weird because I thought this rule would actually take care of copying the static assets

filegroup(
    name = "ui",
    srcs = [":prod-js"] + glob(["resources/public/**"]),
    tags = ["manual"],
)

but I had to do it manually.

To view this discussion on the web visit https://groups.google.com/d/msgid/kythe/7776497f-665a-471a-b727-f49f78939f9bn%40googlegroups.com.

[Kamil Laskowski]

Christian, 

I spent at least 3 hours yesterday trying to find out how to get web ui working without a success. I was trying to redo https://kythe.io/getting-started/ a couple of times thinking that I missed one command which prevented me from starting this http server. Today I hopelessly typed "bazel build kythe web ui" in google and your topic came up. I followed your advide and my server is up and running. It saved me a lot of effort and probably another day of trying. 

Thank you very much for sharing your solution!!!