https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417
--- Comment #266 from David Cook <[email protected]> --- OK just one more comment... Why don't we create a metapackage for koha like "koha-standalone" or "koha-small", which requires MySQL, Elasticsearch, and RabbitMQ (and any other external dependencies which should be run on other servers but don't have to be for a small instance). That could offer an easy setup for small Koha libraries, while leaving koha-common for more experienced and well-resourced Koha libraries and Koha support providers? (Side note: Once we have added RabbitMQ and eliminated our dependence on CGI, and maybe packaged static assets separately, we won't have to include Apache with Koha anymore either. The Apache dependency could be added to that metapackage for novice users, but most of us could replace it with Nginx or HAProxy or some other reverse proxy/load balancer.) In my mind, the koha-common package is going to become smaller over time, as we'll need fewer dependencies running on the same server as the Starman application server. So maybe the best compromise is to retain a common/core package and then have a more comprehensive metapackage which also includes that common/core package. That should make everyone happy? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ 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/
