"#D7CX: I pledge that this module will have a full Drupal 7 release on the day that Drupal 7 is released" might as well remove this from the project page as its been nearly a year since Drupal 7 was released.

CommentFileSizeAuthor
#3 munin-d7-port-1392496-1.diff5.24 KBAlex Savin
#3 munin.zip10.49 KBAlex Savin

Comments

damien_vancouver’s picture

Title: #D7CX removal » #D7CX removal and start work on a D7 port

Hijacking this issue slightly to see what interest there is in getting together a D7 port of this module? The 7.x-1.x branch in git is actually 6.x code according to its .info, so there is no work started yet. The #D7CX should definitely be removed, so as not to confuse people into downloading 7.x-1.x dev by mistake when it contains only broken code. In fact, the 7.x-1.x branch should probably be cleaned out and replaced with a README.txt explaining that the port is not yet started.

I'm interested in helping - I use Munin extensively monitoring my servers, and I'd love to add in Drupal monitoring to the sites too.

But.... things are looking a bit abandoned with this project. Specifically there are two great (alternate) approaches to getting rid of the hardcoded database credentials: #1133544: Refactored for Drush, other changes and #612304: Avoid hard coding database credentials in the script.

In creating a D7 version, it would be nice to discuss and adopt one of those approaches or elements from both before doing the port, seeing as the parse DB URL code all needs rewriting anyway due to changes in settings.php.

So, is anyone a maintainer with access? Is anyone else interested? Should we try and rescue this module from abandonment?

andyf’s picture

I'm also interested in this, and would be willing to put in some time. I haven't used (or taken a look at) the D6 version though.

Alex Savin’s picture

StatusFileSize
new10.49 KB
new5.24 KB

This is a raw port of this module to Drupal 7. I tested it and it worked for me.

As extra I fixed #906984: Users information graph fails and added the possibility to configure a mysql host into the created script.

I plan to actively use this module so I'm thinking to create a second version to enhance it with automatic entity discovery and some more default graphs but also some more hooks.

I could continue the work on this module but i don't know exactly how to become a maintainer of it.

Alex Savin’s picture

Status: Active » Closed (fixed)

The pledge was removed and the work on D7 port is started.