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

Confusion about API vs Federation API during deployment #211

Open
gdevenyi opened this issue Jul 24, 2024 · 3 comments
Open

Confusion about API vs Federation API during deployment #211

gdevenyi opened this issue Jul 24, 2024 · 3 comments

Comments

@gdevenyi
Copy link

Description

The documentation does not make clear the differences between the full-stack federated and non-federated installations, resulting in confusion as to which API path should be proxied in a proxy configuration and which API endpoint the query tool should be pointed at.

Relevant documentation pages

https://neurobagel.org/getting_started/

Additional details

No response

@gdevenyi
Copy link
Author

gdevenyi commented Jul 24, 2024

The form deleted some of what I typed. Cool.

Re-adding.

There should be some kind of state-based description of how the moving parts work under the different 'stack' setups.
"query tool makes a call to X which makes a call to Y which makes a call to Z"

So that the person doing configuration can understand how each moving part talks to each other and can test them.

Copy link

github-actions bot commented Oct 8, 2024

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

  • prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
  • close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
  • archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
    apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
    label in the future. Use sparingly!

@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 Oct 8, 2024
@alyssadai
Copy link
Contributor

@github-actions github-actions bot removed the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants