Josh Soref
Josh Soref
The user of the service (in description) isn't `root` -- I presume that pdns can't access that file.
`/etc` is for me, the admin. It represents my customizations/personality added to a system. If I put something into `/etc/systemd/system/kibana.service`, I expect it not to be stomped upon by a...
https://www.digitalocean.com/community/tutorials/understanding-systemd-units-and-unit-files does a fairly good job of explaining the `/etc` vs `/lib` distinction
Probably the most important thing is that if you (a package manager) put a file in `/etc/systemd/system/something.service` then i can't safely use `systemctl mask something.mask`, because that would more or...
See probot/probot#803
Surely this could be supported with either a `toJSON` / `fromJSON` or by taking a file parameter which contains the relevant content.
It doesn't seem like they'd accept a community contribution without first showing demand. But you could make a fork that included it and the evidence of repositories using your fork...
@yeikel why not create a branch in your fork that adds the support and then link to it here. We'll be able to see how much your repository is used...
🤷 There's no obligation to maintain your fork. This repository doesn't have high churn and you aren't obligated to support it. For anyone curious, adding support for a distribution really...