-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add Memgraph support #99
base: main
Are you sure you want to change the base?
Conversation
config.yaml.example
Outdated
@@ -16,6 +16,14 @@ integrations: | |||
config: | |||
AUTH_TOKEN: example-token | |||
ORGANIZATION_SLUG: example-organization | |||
storage: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this is just an example file, but we technically can't have two storage
entries in a valid config file. I'd recommend creating a separate example file for showing a Memgraph configuration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I created another config.yaml.memgraph.example
, the name might be too long and I can change it if necessary
config.yaml.example
Outdated
config: | ||
username: | ||
password: | ||
uri: bolt://localhost:3000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is port 3000 listed here the default port for uploading data to Memgraph? I'm by no means an expert at Memgraph, but I was under the impression that like Neo4j it uses port 7687 for the bolt connection to upload data.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are completely right, Memgraph uses the same port. Memgraph Lab has 3000 for the visualization part so this was a bit of a "tip-feller" from my side
- '7444:7444' | ||
- '7687:7687' | ||
volumes: | ||
- mg_lib:/var/lib/memgraph |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these the correct volume paths? It looks like you added docker/.memgraph
to the .gitignore file, but these all look like they'll be in individual folders and not within a .memgraph folder.
Thanks so much for the contribution! I'm assuming based on my initial look at the PR that we'll want to complete the SDK contribution first to expose the additional memgraph commands, but I went ahead and put in a few small comments here. I'll go have a look at the SDK PR here shortly. Thanks! |
So sorry for the late response. I've added another commit where I agree with your comments and fixed stuff mentioned. Feel free to let me know if there's something else you noticed, thank you! I'll also get to the sdk PR asap :) |
Hi, I'm Matea, Memgraph's Developer Experience team member.
Recently I've been deep diving into your amazing Starbase project and decided to enhance its compatibility with Memgraph. I adjusted a few files and queries in order for them to work with Memgraph, and ensured seamless integration.
I've also taken the initiative to create a pull request for the integration of Memgraph's SDK CLI for full compatibility.
Looking forward to your feedback!