Make the config edit easier

[pyrooka]

I would like to make the configuration edit easier (e.g. for my team members).
I am thinking about a minimal web UI to edit the yaml in runtime. What do you think about this @rycus86 ?

Somehow related to #6 , because if we don't need to restart the container often, the startup messages are fine.

[rycus86]

Hm, interesting idea!
I'm not a huge fan of editing files at runtime, especially in a container context, because it might get tricky about how you bind mount it, what if you have multiple nodes, etc.
At the moment, SQlite is pinning this to a single node anyway, so maybe not a huge problem, but 🤷‍♂️

What about allowing saving dynamic configuration in SQlite? Then on startup, it could read both the config file and the dynamic config from the database?

I'm not totally against the file edit either, but it feels like if there's a database already, perhaps use that.

What do you think?

[pyrooka]

Good point.
I'm running this app on Kubernetes and volume binding is not allowed. This is why I didn't think about what you're saying, but yeah, you're right.

So what if on startup it reads the config and loads it to the DB, then at runtime the app only modifies the DB? Maybe create a function to download the config in yaml to make the backup easier would be great.

So?

[rycus86]

Yeah, that's a good idea!
You could have the configuration loaded from a URL at startup, then just use it, no need to write it to a file I believe. The only thing to consider is how to reload it when it changes, if that's a concern. You could simply restart the pods in k8s, or maybe we'd need some way to trigger reloading the config in this app.

[pyrooka]

Okay, let's see what can I do!

[pyrooka]

I don't have too much spare time these days so this may take a while. 😕

[rycus86]

I know what you mean. 😔
I'll help you review PRs when you're ready, I don't think I'll have any time to look into implementing this either sadly.