Hello Community. I am trying to set up a locally installed Ory Hydra to sit in front of Google OAuth b/c DCR is required. I am hosting a local

ory-network

with docker compose consisting of hydra, Postgres and the consent app here

oryd/hydra-login-consent-node:v1.10.6

. Are other parts of the Ory ecosystem required for this. I've hit a bit of a road block and wanted to make sure i was on a good path. When setting HYDRA_ADMIN_URI in login-consent to my

ory/hydra

instance, it is set back to

<http://hydra:4445>

. Also Github mentions a

services/hydra.js

Yet, that is not in the final image. Apologies for multiple questions, extra information/queries included to weigh in on if i'm on the wrong track or not.

Hey @icy-school-14408 I believe that configuration (hydra, postgres and consent node) is good enough for setting hydra locally. Is there a specific issue that you're facing while setting ory hydra up?

Hey now @blue-knife-89618 Thank you, i was a bit confused if i would need Kratos etc for an Oauth2 Flow. hydra-login-console with another docker container running hydra and one with postgres were indeed enough. I may ask this in a main thread, but if you happen to see this. Is

queryParamsStringify

meant to be removed? I see the library is deprecated, yet it remains in

hydra-client-fetch

and

client-fetch

, yet when running inside the

hydra-consent-node

i received

this.configuration.queryParamsStringify is not a function

I can add the library back, but seems like removal was intended and appropriate. Thank you!