Plugins administration WebUI part II

After rethinking the plugin functionality i realized that the current implementation does not reflect my requirements. It should be possible to upload plugins via WebUI (which are added to a local APT archive then) and the WebUI should also display plugins that are in the OMV package web archive. So i refactored the WebUI and backend to meet these requirements. It is only possible to install OMV plugins via WebUI (no other *.deb packages), so the packages must meet a naming convention, otherwise the backend denies uploading and installation.

Note, OMV plugins only contain the files required by the framework, e.g. the scripts, WebUI javascript and backend PHP files. The package(s) the plugin requires additionally are defined as package dependencies (get more informations here and here), this means the NAS box must have I-Net access to download these additional packages during installation.

I do not plan to implement a special plugin package management that does not need network access to get these additional packages (which means the additional packages are included in one big file).

10 thoughts on “Plugins administration WebUI part II

  1. Hey, very clever idea!

    debians package management is well known an rock stable – perfect for this task.

    /thorsten

    P.S.
    Ich freue mich auf eine Beta, werde sehr gerne testen und helfen!

  2. Do you check the contents of the plugin or is it possible to install deb-package following the naming conventions (renaming binary deb-packages to match plugin naming conventions)?

    Is it only possible to use official debian packages as depends?

    Is an online repository planned for the future?

    • Do you check the contents of the plugin or is it possible to install deb-package following the naming conventions (renaming binary deb-packages to match plugin naming conventions)?

      Hey thanks, i have to deny this.

      Is it only possible to use official debian packages as depends?

      Yes, otherwise you won’t be able to use the great number of official deb packages.

      Is an online repository planned for the future?

      Yes, this will be the home of the OMV plugins and spezial (backport) packages.

  3. That’s so nice. I hope sabnzbd comes as one of the first plugins.

    Thanks a lot, I’m looking forward to the launch of OMV.

  4. Sounds like a good plan.

    Since you’re already working on extensibility and the about page, is it right to assume you almost have everything you want in place for the base system? Which services are still missing?

    • No, there are still many things to do. Don’t ask me what, because i can’t tell it due i do not have my todo list here right at the moment.

Leave a Comment