[Question] Open Source module list

[yyvess]

With the aim of exploring Timoni, I have begun developing a Timoni module for deploying Keycloak .

Is there a specific location where existing Timoni Bundles are listed?

If anyone has the time, I would greatly appreciate feedback on my Timoni module:

https://github.com/yyvess/keycloak-timoni

Inside the test folder, you'll find some sample value files along with YAML files produced from these values. Thank you in advance for your time and input.

[Nalum]

Awesome! I'll have a look through a little later when I have more time. Might open an issue on the repo with suggestions if I have any!

One example being:

https://github.com/yyvess/keycloak-timoni/blob/alpha/templates/config.cue#L142

You have this as an optional field but don't set a default, might be better to have it as required envs: KC_DB!: if you don't want a default value or not optional but with a default envs: KC_DB: *"dev-file" | .... I should note I'm not familiar with keycloak so this may not be a good change for this env var.

I also spent some time setting up a module which you can look at to see another example.

[stefanprodan]

We could create a dedicated page in timoni.sh website and list there open source modules and link to their Git repo, OCI source and readme. Ideally we would make ArtifactHub compatible with Timoni modules and have them listed there, ref: https://github.com/stefanprodan/timoni/issues/73

[GeorgeMac]

As per @stefanprodan suggestion, I have come to share our little module repo over at Flipt: https://github.com/flipt-io/timoni-modules

It contains two modules:

• Flipt
• Traefik

Maybe it makes sense to break these out across multiple repos, but thought I would start with one repo for now. We're evaluating Traefik for an internal project, that is why I added that one too.

[b4nst]

We've also opened loft-orbital/timoni-hub to the public. It's super early stage in term of modules. None are prod ready yet, as we only use timoni on private dev environments for now (discussion about migrating to prod are happening internally).

However the build and release system along with the contributing guide are mature. We put most of our efforts there first because we believe this is what would be the heaviest barrier to adoption. With that in place it's now easy to maintain and upgrade modules, or to create new. We will add and start maintaining every non core business modules we have internally.

Hope it can help the community!