Keto Quickstart is outdated

[alfa-alex]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Ory Network Project

No response

Describe your problem

The Keto Quickstart is based on keto v0.7.0-alpha.1. This is confusing because the instance started by this is not consistent with the API docs that assume the latest keto version (for example, regarding the handling of a non-set max_depth). Updating the version yourself easily is made difficult by the following factors:

• the Docker image used in the docker-compose of the cat-videos-example has a -sqlite suffix; on Dockerhub there is no no -sqlite version later than v0.8.0
• even for non--sqlite versions the latest Dockerhub-published version is v0.12.0 whereas the latest release is v0.13.0 (means you don't automatically publish a new docker image with every release)
• the contrib folder hasn't been updated for a while: the relation-tuples/*.json contain a "$schema": "../../../.schema/relation_tuple.schema.json", line that doesn't seem to be supported by more recent version of keto (if I am mistaken, please answer here and I'll update this issue accordingly)
• the docker-compose.yml's init container command lacks the --insecure-disable-transport-security=true argument that is required in newer versions of the keto CLI (same holds true for all the CLI commands mentioned in the Quickstart).

After some research I could find out that I can actually use the project's Dockerfile-build via the build make target and just needed to update the folders in the docker-compose.yaml from /home/ory to /home/nonroot. Putting together all these pieces I was able to run a current version of keto via docker.

It would be nice if you could update both the examples and the Quickstart guide. In any case, I hope this issue might help other newcomers who run into the same problems when trying to run a recent version of keto.

Describe your ideal solution

• Quickstart is updated to the latest keto version
• docker hub images are kept up-to-date with new releases

Workarounds or alternatives

Does not apply.

Version

v0.13.0

Additional Context

No response

[nmapx]

I have the same feeling about keto. Once you get started with Hydra/Kratos it's much easier to add other products like Keto and Oathkeeper to the stack. But starting with Keto and outdated documentation might be a problem for less experienced developers.
Docker images are usually released right away (was never a problem for me) but indeed v0.13 was published already but the image in registry is missing. The whole topic of Keto releases should be discussed since it's in alpha for a long time now and what is the future of this project in overall in that case?

[github-actions]

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

• open a PR referencing and resolving the issue;
• leave a comment on it and discuss ideas on how you could contribute towards resolving it;
• leave a comment and describe in detail why this issue is critical for your use case;
• open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️