[Koha-devel] Distributing Koha Plugins efficiently

[Michael Hafen]

Nope, I run the plugin install script by hand as necessary.  I don't see
system-wide plugin updates very often.  A git commit hook script would be
handy though.

On Thu, Jun 23, 2022 at 8:02 PM <dcook at prosentient.com.au> wrote:

> Thanks for replying, Michael. I am leaning towards a Git repo as well for
> the sake of simplicity. I imagine you have a script in that repo for
> running “koha-foreach perl /usr/share/koha/bin/devel/install_plugins.pl”,
> restarts, etc?
>
>
>
> David Cook
>
> Senior Software Engineer
>
> Prosentient Systems
>
> Suite 7.03
>
> 6a Glen St
>
> Milsons Point NSW 2061
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
>
> *From:* Michael Hafen <michael.hafen at washk12.org>
> *Sent:* Friday, 24 June 2022 2:16 AM
> *To:* dcook at prosentient.com.au
> *Cc:* koha-devel <koha-devel at lists.koha-community.org>; Tomas Cohen Arazi
> <tomascohen at theke.io>; Kyle Hall <kyle at bywatersolutions.com>
> *Subject:* Re: [Koha-devel] Distributing Koha Plugins efficiently
>
>
>
> That's basically what I have done, except that I distribute my plugins to
> my servers from my git repo.
>
>
>
> On Wed, Jun 22, 2022 at 9:52 PM <dcook at prosentient.com.au> wrote:
>
> Hi all,
>
>
>
> If I were to unpack 5 different Koha plugins to /opt/koha-plugins and then
> added "<pluginsdir>/opt/koha-plugins</pluginsdir>" to the koha-conf.xml for
> all my Koha instances, I should be able to just run “koha-foreach perl
> /usr/share/koha/bin/devel/install_plugins.pl” to install/upgrade all
> those plugins within Koha, right?
>
>
>
> Once “bug 21366 – add plack reload” is done, we could then do “koha-plack
> --reload $(koha-list --enabled --plack)” to gracefully reload all those
> Koha instances to have the freshest version of the plugin.
>
>
>
> --
>
>
>
> If that’s true, a person could bundle Koha plugins however they like,
> right? They could put them into koha-common, they could do their own
> koha-plugins package (included or separate to their Koha codebase), they
> could just use a Git repo, or whatever makes sense for distributing. The
> advantage of Debian packages would be adding that “koha-foreach” and
> “koha-plack” into package install hooks.
>
>
>
> I suppose a “install plugins” hook in “koha-create” would be wise too so
> that a new instance could auto install any centralized plugins…
>
>
>
> Does that all make sense? Am I missing anything?
>
>
>
> I’d really like to use plugins in lieu of Koha customizations but I find
> distributing the code across a large number of Koha instances to be
> prohibitive.
>
>
>
> David Cook
>
> Senior Software Engineer
>
> Prosentient Systems
>
> Suite 7.03
>
> 6a Glen St
>
> Milsons Point NSW 2061
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
>
>
> --
>
> Michael Hafen
>
> Washington County School District Technology Department
>
> Systems Analyst
>


-- 
Michael Hafen
Washington County School District Technology Department
Systems Analyst
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220624/f27ff544/attachment.htm>