Skip to content
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

graph viewer webui #737

Merged
merged 28 commits into from
Feb 13, 2025
Merged

graph viewer webui #737

merged 28 commits into from
Feb 13, 2025

Conversation

ArnoChenFx
Copy link
Contributor

@ArnoChenFx ArnoChenFx commented Feb 9, 2025

Because I plan to refactor the original web UI and integrate it, I've renamed it from graph_viewer to webui for now.

Here are the steps to experience the graph viewer webui:

  1. Build the frontend project according to this guide.
  2. Set the graph database backend to neo4j (currently only the neo4j backend implements the /graphs API).
  3. Start the lightrag server. assuming the server is running at http://localhost:9621.
  4. Open a browser and visit http://localhost:9621/graph-viewer.

TODO

  • Visualize properties of node.
  • Visualize properties of edge.
  • Navigate between nodes based on relationships.
  • Add more parameters to make it more configurable.

Future work

  • Enable more backends to implement Graph-related APIs.
  • We need a super cool logo!

Screenshots

Properties-View

2025-02-09

image

image

Demo Video

Demo Video

PixPin_2025-02-10_22-09-19

format
@ArnoChenFx ArnoChenFx changed the title WIP: graph viewer webui graph viewer webui Feb 13, 2025
@ArnoChenFx
Copy link
Contributor Author

@LarFii DONE!

@LarFii LarFii merged commit 3661850 into HKUDS:main Feb 13, 2025
1 check passed
@ArnoChenFx ArnoChenFx deleted the graph-viewer-webui branch February 14, 2025 05:32
@ArnoChenFx ArnoChenFx mentioned this pull request Feb 20, 2025
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants