Janitor 3PC for revo

From this thread http://modxcms.com/forums/index.php/topic,46028.0.html an idea I’ve had for a while is taking shape more, to quote from the thread

Janitor is just an idea I’m having to help people do site maintenance, like a janitor is responsible for building maintenance. I’m not sure yet exactly what’s needed but we can have tabs for this for DB stuff, some MODx specific stuff like truncating manager logs etc. permissions checks, maybe a backup/restore facility maybe other stuff that I can come up with and code. I’m kinda interested in timed events, i.e a nice interface to crontab, or even MYSQL’s event handler.

In other words a sort of MODx specific toolbox to help with everyday site maintenance concentrated into one point.

OK, anybody any ideas on what’s wanted/wished/needed here besides mine?

Screen shots of where we are so far below.

One thing I’m missing in your suggestions are the possibility to delete ressources there are flagged un-published directly, and executed by the crontab. And - but maybe out of scope - some sort of mailer to a admin in case there are anything in the error log?

Truncating the logs would be good. I’ve thought about having a "prep for update" button, especially when using the development version:

delete core/packages/core
delete core/packages/core.transport.zip
empty the logs
clear the cache
flush permissions
flush all sessions

This would be great... SQLBuddy for DB stuff, integrate or write something like phpmybackuppro for
backing up stuff, PHPIDS for security (somebody did this for EVO already)....

PHPIDS

this sounds like a good candidate that I hadn’t considered, especially if Evo already has one.

OK, I’ve integrated phpmybackuppro, screenshots below, at the moment these are just pulled in as iframes, hence you get the full app, all I’m doing is just changing them enough to secure access only from Revo, not externally, this leaves both of them showing login screens as you can see.

Question, do we want this or do we want to hard code database params from the config.inc.php file and go straight in as it were.

Pro’s are we become tied to the Revo database so we can’t do any damage anywhere else and it looks slicker.
Con’s are we lose flexibility, some people may want to log in as admin users to do stuff, not normal/webusers, especially with mySqlBuddy.

Just wanted to chime in with support for this effort and I love the name.

Yep, now I’ve started it and stopped just mulling it over I’ll push this forward, put some more meat on the bones to get to beta 1 then push it out to GitHub.

@shamblett You are The One!

This is awesome. Looking forward to using it asap.