| 18 May 2023 |
 emily | In reply to @m1cr0man:m1cr0man.com
Thanks for jumping in there emily 🙂 I always feel a pressure to respond to these sort of issues (when someone is eager to open a PR) to make sure the module stays maintainable, it's good to know I'm not the only one looking out! no worries, sorry i'm barely around these days :) | 06:03:37 |
| emily | I was thinking CPUWeight=idle, didn't know about CPUSchedulingPolicy. I wonder what the difference is :/ | 06:04:31 |
| emily | I agree that the module is definitely plenty complex enough already (honestly too much in my opinion, I am quite down on lego at this point with how much it has required in the way of custom-built infrastructure and workarounds) | 06:06:05 |
 m1cr0man | Heh I'm barely around either so don't sweat it... I wish I had time to do more, such as opening PRs to Lego to upstream some features like offline renewal checking and proper handling of domain list changes. If they are resistant to those sort of things I'm not against beginning to migrate the module to another tool but... So many resources out there wrt setting up acme as well as people's configs rely on Lego. It's a bit vendor locked sadly | 08:17:58 |
| emily | yeah I feel like the last migration was painful enough that rewriting the whole thing yet again and probably breaking people's configurations in the process would hurt. | 08:34:38 |
