Clearly the cloud approach is what you want people...
# general
a
Clearly the cloud approach is what you want people to adopt, I get that - but the products are still open source and benefit from community contributions 😕
s
We're just unifying the docs, so it is shares all the content that is the same. Most of the time there should be tabs that let you see how to do something in one or the other deployment mode. The page you referred to explains mostly concepts, which are exactly the same no matter how you use Ory. In the end it also has the raw json config example, which is exactly what you need to set for self-hosting as well. Regardless, we know that the docs are not ideal in all parts, and especially explaining the differences between self-hosted OSS and other means are something we are constantly looking to improve. We have noted the feedback, and are always grateful for this type of input.
a
Are you referring to the YAML labelled "ory get identity-config --format yaml" at the bottom of this page ? (the CLI command that, to the best of my knowledge, is only of use to Ory Network users and provides tunneling support?) I get your overall point, but: If you read this: > Ory Actions are an extensibility mechanism provided by the Ory Network that allows you to integrate with third-party services > You will (fairly, I think) assume that there is no such equivalent in the individual products (Hydra, Kratos etc), even if this is actually a shared concept that works across both self-hosted OSS deployments and SaaS customers. That's not clarified anywhere
And it's frustrating because there used to be perfectly good documentation here!