Mastodawn

Hi @[email protected], We’ve received similar feedback from other users, so we are currently working on it. However, this requires changes to some internal processes, as the system was not initially designed this way. Thanks for the feedback!

Show thread

tripping335 3d ago

Personally, I think going local file config first was the right decision, depending on what the target audience is. For homelab users with one or two databases it may seem like extra work. For professionals or advanced users who like, or even need, to automate using tools like Ansible etc this makes it easier to deploy on larger scale. You can of course allow users to update settings after the fact through the UI while keeping the json file. I have dropped projects in the past due to the exact issue that its only configurable to the UI that makes bulk operations or automation hard or impossible.

I’m currently using shell scripts (pg_dump) and crontabs to back up my databases, so thanks, will check it out!

Show thread

KillianLarcher 3d ago

Thanks for sharing your use case. To be transparent, we didn’t consider automation when we created the local file config, but it’s indeed the perfect use case for this mode of operation. In any case, we’ll keep the current behaviour to avoid breaking changes. This will be introduced as an additional feature.