-
Notifications
You must be signed in to change notification settings - Fork 49
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
[Feature Request] Allow saving/sharing connection details #111
Comments
If you are on the connections page and click on a previously created connection, there should be a downward pointing arrow icon that is for exporting the connection. If you hover over it, you should see "Export Connection". Conversely, in the "Available connections" panel, you should see an upward pointing arrow that is for importing the file that you exported via the export button. If you want to store these files, you'll need to export the connection and manually place it in some storage system and then the next user will need to import it themselves. |
This function seems to work on a single users browser, but trying with another user/browser, the import seems to only bring in the connection details and not the styling as described. I have a workaround to hack out the database to JSON (via console) and then import on a new machine, however this would be much better if the connection export and import would work across browsers/sessions/PCs To test, export a connection with styles, then try to import into a incognito session and you will see that only the connection is imported and none of the styling. |
Closing SummaryI'm closing this issue because the original feature request exists within the app already.
You can share that file with whomever has permissions to access the database in question. In their browser you will import that file.
The connection will be created and a schema sync will be automatically started. Once complete the connection is available for use. Other CommentsThere were a few comments about sharing style config to multiple users. There are a few existing feature requests for this.
There was also a mention of copying the entire local database and restoring it to another browser. This is a feature added to Graph Explorer v1.10. One caveat is that the restore process will replace all existing config data. So it is best used for initial setup, not continuous sharing. |
Community Note
Graph Explorer Version (and Graph Database and Version used if applicable)
Any
Is your feature request related to a problem? Please describe.
Enhancement
Describe the solution you'd like
I want to have the ability to save the connection details server side, or in a shareable method, so that other members of the organization can access graph explorer and connect to the same database without needing to configure the connection again
Additional context
The text was updated successfully, but these errors were encountered: