docs: Better systemd unit file for AI workers - #15509
liamdennehy wants to merge 1 commit into
Conversation
The original method added complexity of a script file which requires `chmod +x`, runs sudo on each invocation (which can spam logs), and does not invoke `systemctl daemon-reload` before starting the units leading to warnings (though not fatal). This new flow uses systemd's own execution environment (including handling the user) and simplifies the dependencies. Activation is also streamlined since systemctl can handle multiple units in one command, avoiding shell `for` loops. Signed-off-by: Liam Dennehy <liam@wiemax.net>
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
1 participant
The original method added complexity of a script file which requires
chmod +x, runs sudo on each invocation (which can spam logs), and does not invokesystemctl daemon-reloadbefore starting the units leading to warnings (though not fatal).This new flow uses systemd's own execution environment (including handling the user) and simplifies the dependencies. Activation is also streamlined since systemctl can handle multiple units in one command, avoiding shell
forloops.☑️ Resolves
🖼️ Screenshots
Before:
After (apologies for the awful render):
✅ Checklist
codespellor similar and addressed any spelling issues