Closed alyssadai closed 10 months ago
For reviewer, see on st-viateur
:
~/projects/pd_compose
pd_compose_default
(default name based on compose config location) using:
docker network inspect pd_compose_default
curl -u "admin:<PASSWORD>" http://localhost:7200/repositories
Thanks @alyssadai! All config files look great, excellent choice of credentials. However I am getting error 403 from the QPN API:
{"detail":": Forbidden (HTTP status 403)\n"}
I'm assuming that's not what we want?
Thanks for catching that @surchs.
I've re-granted RW permissions to both the mni_qpn
and mni_ppmi
databases for the database user I set up. If you try to access the QPN API again it should now work.
I've also opened an issue to document the (problem of) non-additive GraphDB permissions here https://github.com/neurobagel/documentation/issues/116.
Hey @surchs, following recent discussions about the privacy of QPN I've updated the API config for the mni_qpn
database to run in aggregate mode as well.
Let me know if this issue looks good to close now 🙂
@alyssadai I checked the requests and it now works for me with no auth error! Thanks a lot. I think we can close
Ideally, these datasets would live on two different different databases (with different APIs) in the same graph server.
In order to allow two different APIs to talk to the same graph container, we may need to create a new docker-compose.yml or otherwise connect one of the API container to an existing docker network (see https://docs.docker.com/engine/reference/commandline/network_connect/).
Steps to implement
st-viateur
and add two new PD databases (mni_ppmi
andmni_qpn
)api_qpn
along with graph stack in ~non-aggregated~ aggregate modeapi_ppmi
in aggregate modeapi_ppmi
toapi_qpn
Docker network (arbitrary) and ~rename network~api_ppmi
can reach a db in the graph container~/projects/pd_compose
st-viateur
to allow ingress on each new API's port