I haven’t put too much thought into this yet. A "branch" depth threshold is the first thing that comes to mind, with RBD flattening as an option once that threshold is reached.
oh yeah, sorry, I should've started my comment with "this is awesome" because it is, you did a great job explaining all the layers and the interactions within. I love stuff like this even if it's not necessarily prod ready by default!
I am not sure where you think I claimed it'll be "easy and quick". Do you really think building a system on top of k8s internals and Ceph is something that everybody can pull off?.
It's far from complete. This is just the infrastructure bit that I need to build the actual service. I am going to build an operator, a coordinator, an API and a CLI. I am going to continue writing posts while building them.
Hey HN, I vibe-coded a small self-hosted phonics flashcard app for my daughter this afternoon. She has an "exam" next week based on the words in the data folder. If your kids struggle with phonics, you can use this too: generate word lists with any LLM, drop them into the data folder, and follow the README.
This looks great though I like TUIs more. I’ve been using https://github.com/idursun/jjui for the last few months, I highly recommend it if you are a TUI person like me.
Yeah the TUI ecosystem is much more built out than GUIs for JJ so far. TUIs are great too - over time I've personally found myself ~50% in the CLI and ~50% in some sort of GUI, but a TUI can fill both gaps pretty nicely. I have always hated viewing diffs in the terminal though.
