https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40901
--- Comment #2 from David Cook <[email protected]> --- (In reply to Tristin Stagg from comment #1) Thanks, Tristin, for all that info. I agree with a lot of what you're saying here. That said, I think there are some challenges with it. Generally speaking, SystemD isn't available in Docker containers, so this isn't going to work for koha-testing-docker. If we were to more fully embrace SystemD, we'd need to have viable alternatives for koha-testing-docker to function. But if we did have alternatives for koha-testing-docker to function, it wouldn't really be testing Koha as much as we are now. I don't think that's necessarily a blocker, but it's something that would need to be carefully considered. > Suggested Fix: > > 1) Replace the init.d style management with native systemd unit files for > each Koha component. > 2) Use templated units for instance support ([email protected], etc.). > 3) Have koha-common.service or koha.target depend on these per-instance > units. > 4) This would align Koha with best practices for systemd-based services and > improve stability, observability, and maintainability in production. I have a different system I deploy using Debian packages and I have "debian/pkg.app.service" and "debian/[email protected]" files where "debian/pkg.app.service" depends on "[email protected] [email protected]". It works well, but it is also built into the package itself which lives in the git repo. I am curious how we'd use SystemD templates with Koha's dynamic instance management with that dependency in mind. This might be possible and I'm just not familiar enough with unit files to know how to do it. It's just a concern that comes to mind at the moment. (After doing a bit of Googling, it looks like it might be possible to provide a "foo.service.wants/" directory. I suppose a person might also use an *override.conf file. I hadn't thought of that before although I've used those in other places for other reasons.) -- So overall... I think it sounds good. The only sticking point I can think of is koha-testing-docker. But maybe that will become clearer as we re-tool the SystemD files. Interesting idea in any case! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
