CereusUpdates - Auto-Install Templates and Plugins

[phalek]

Hi,

I'm currently working on a plugin which allows cacti admins to install plugins and new templates from within the Cacti user interface without the need to go to the command line.

It will include update notifications for new versions as well.

It will come with 2 options:

Free version: Ability to Install current plugins and templates. Plugin/Template developers can "hook" in here as well easily. No guarantee for plugin compatibility with installed Cacti version
Supported version: includes 100% compatibility checks of plugins with most current Cacti and PHP versions ( excl PHP 7 for now ).


It's currently in early development, but basic functionality ( installing a plugin ) already works.

Once I have a working version ready ( within the next days ) I will need some testers for it, I need to have at least 5, up to a max of 10 testers, all which will get unlimited access to the supported version once released.

Please PM me if you're interested, send me an email or post here with the following information:

Code: Select all

Operating System   : Centos / Ubuntu / Windows 2012 
OS Type            : 32/64bit
Cacti Install Type : apt/yum | CactiEZ | windows installer | source
Current Plugins    : Thold, settings ...
Plugin Wishlist    :
Template Wishlist  :

Thanks.

[cigamit]

CactiEZ has something like this in its "setup" plugin. A new packaging system has been developed using signed XML packages for both plugins and templates. This is also being integrated directly into the Cacti 1.0 setup, and will be combined into the importer going forward.

[phalek]

Yes indeed, but. It doesn't really check for any updates and it (currently) works only for plain xml templates. Not sure if it does check on pre-reqs or OS depencies.

I'd like to take this all into account and additionally provide the service of actually testing the templates and plugins against specifc Cacti/PHP/OS versions, so users can be sure these can be used/installed. This is something a few corporate users will probably value.

Nevertheless, I liked that "setup" plugin, and signing the packages does make sense somehow, but then this also limits the possibility to have external plugin or template developers take part in this.
A simple sha based hash probably does the same thing and would allow external/3rd party providerd to hook into this.

Well, I guess this was all planned long ago with the "repository" tab at the top of this page ...


That said. Thanks cigamit for taking an active role in pushing Cacti down to 1.0 and I'm sure there are lots of users that will just be fine with what Cacti is offering and don't require additional tools or plugins like the one I'm currently developing.

[cigamit]

Yes, it was planned and mostly developed over 8 years ago, but never really came fully into fruition. I had programmed a full repo / developer environment that allowed any developer to create an account. It created svn repos, allowed you to grant others access (generated ssh keys), push and packaged new versions, automatic changelogs, dedicated bug tracker, forum, information page (with screen shots), rating system, download counters per version, etc... packages had to be "vetted" before they initially would go out. And a good bit more, it was nearly 100% completed but I'm no frontend designer, so I hated the design I had. The original update plugin that checked for plugin updates worked with it, I had made some changes that would then download the plugin and (if it had access) update the plugin for you (or re-import the template). If the webserver didn't have write access, it came with a command line script that would do the same.

The packaging system is mostly what I retained from that. The packager should work with any template, I believe I had several that used script_server scripts, etc.... In the future we should also have a "developer" key / unsigned that will work, but it will warn users that they are using a self signed / unsigned package. Everything is complete flux at the moment.

[phalek]

Understood.

It's they're any possibility to support the team with testing/packaging templates and plugins or take part in developing this part ?