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

[ENHANCEMENT] Pick some reasonable default username for the DB communication #119

Closed
gdevenyi opened this issue May 24, 2023 · 2 comments · Fixed by neurobagel/documentation#92
Assignees
Labels
documentation Changes only affect the documentation quick fix Minimal planning and/or implementation work required.

Comments

@gdevenyi
Copy link

gdevenyi commented May 24, 2023

DBUser or such

Make sure stardog and graph db use the same name
See also neurobagel/documentation#74

@gdevenyi gdevenyi changed the title [ENHANCEMENT] Pick some reasonable default username for the API access [ENHANCEMENT] Pick some reasonable default username for the DB communication May 24, 2023
@github-actions
Copy link

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Aug 17, 2023
@surchs surchs added the flag:discuss Flag issue that needs to be discussed before it can be implemented. label Sep 21, 2023
@surchs
Copy link
Contributor

surchs commented Sep 22, 2023

We have that here: https://github.com/neurobagel/documentation/wiki/Alternative-Graph-Backend-deployment.

Maybe as part of neurobagel/documentation#74 we can bring that to both deployment docs

@surchs surchs added flag:schedule Flag issue that should go on the roadmap or backlog. and removed _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again labels Sep 22, 2023
@rmanaem rmanaem moved this to Backlog in Neurobagel Sep 22, 2023
@rmanaem rmanaem removed the flag:schedule Flag issue that should go on the roadmap or backlog. label Sep 22, 2023
@surchs surchs added documentation Changes only affect the documentation and removed flag:discuss Flag issue that needs to be discussed before it can be implemented. labels Sep 22, 2023
@surchs surchs moved this from Backlog to Specify - Active in Neurobagel Sep 22, 2023
@alyssadai alyssadai added the quick fix Minimal planning and/or implementation work required. label Sep 24, 2023
surchs added a commit to neurobagel/documentation that referenced this issue Sep 25, 2023
@surchs surchs moved this from Specify - Active to Implement - Done in Neurobagel Sep 25, 2023
@rmanaem rmanaem moved this from Implement - Done to Review - Active in Neurobagel Sep 25, 2023
@surchs surchs self-assigned this Sep 25, 2023
surchs added a commit to neurobagel/documentation that referenced this issue Sep 26, 2023
* Explain the difference between backend and graph

* Explain license differences

* Explain changes to env variables

* Describe initial security setup

* Adding DB user

* Split upload instructions for graph backend

Fixes #93

* Use consistent user name templates across both backends

Fixes neurobagel/api#119

* Also talk about query tool

and show it with a nicer figure
@github-project-automation github-project-automation bot moved this from Review - Active to Review - Done in Neurobagel Sep 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Changes only affect the documentation quick fix Minimal planning and/or implementation work required.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants