Julian
Julian
the code of your quiet part looks wrong to me. according your doc block it says don't print update message if quiet flag is true but the if code looks...
having a sops config file with `unencrypted_comment_regex` like that: `.sops.yaml` ```yaml creation_rules: - unencrypted_comment_regex: sops:dec ``` and a `secrets.yaml` ```yaml # server credentials credentials: # this is the age key...
### TL;DR providing a unified, consistent experience for developers across all hetzner products would be such a win for your customers. we dream of having one tool to rule them...
similar to the old bug #421, when i turn off the internet over night the background update check leads to an exception Stacktrace: ``` de.marmaro.krt.ffupdater.background.exception.AppUpdaterRetryableException: Simple network test was not...
wouldn't it make sense to tag releases in this repo?
it would be nice to create tags for this repo, so you can subscribe for releases on this repo.
currently the php.ini files are loaded with comments and settings which are default. it would be a good thing to be able to purge these, like it is already possible...
for reducing incoming messages it is handy to subscribe "releases" on a repo. where in this case releases could created after x apps or each month, ...
Removing the requirement of installing docker locally or creating a bitbucket&github account to create (automated) builds would be awesome. would love if you add an option to uploading/copy and paste...