common Helm library.
Ah, didn't know that. I thought everything was configurable via env variables (which I've always found easier to manage), but I'll go ahead and use the config instead.
common Helm library.
Gotchya, I'll rename that to be api instead. I saw backend in the docs like you said, so I just ran with that.
common Helm library.
@konrad I can finish this up this weekend if you're still interested in this approach. If not, I'll just keep it on pause :)
No, the Helm chart could run only an API pod, or only a Frontend pod if configured as such in the values.yaml of the “new” Helm chart :). @konrad
common Helm library.
I'm essentially trying to mirror what Immich is doing here: https://github.com/immich-app/immich-charts
But of course for Vikunja, and allowing a user to set up:
- Backend
- Frontend 3.…
common Helm library.
This chart should create all the resources needed now, just need to do some brain gymnastics of what URLs to set the Frontend/Backend to by default...NodePorts perhaps?
common Helm library.
@konrad using two Ingress objects more easily decouples the api from the frontend, incase a user would (for some reason) just want to stand up either the API or the Frontend. That way,…
I can take a crack at it - if you’re willing to use another extensible Helm chart :)
If the URL doesn't work as a limit of the API, would it be best to just not include the URL as a comment? Perhaps don't include a comment by default when including an attachment, or just say…