Nice interface, but it's a bit strange to me that it uses shell exec for every kind of measure.
e.g. # uptime.php <?php echo (int) (shell_exec('cat /proc/uptime')/(60*60));
Be careful of any externally controllable strings which might allow XSS and give panel access to an attacker.
More of a problem for admin dashboards which have two-way control, which this one must if it can do on-demand refresh.
That's why I prefer munin static pages.
Very cool.
How difficult would it be to create widgets that show application-level stats like number of visitors on site or conversion rates (e.g. calculated from google analytics).
I'm tired of having to loging to google analytics, lulu.com, and gumroad in three different tabs....
Not much different than conky...except the web service part.
Neat, I'd like this to monitor my Pi... Just because I can.
I made similar dashboard app a year ago, written in python with extensible and configurable metrics https://github.com/Eyjafjallajokull/aboco also supports application-specific stats.
you sure you don't want to make a go at turning this into a full blown product? Imagine a more modern version of webmin. Very nice.
Better idea: output the output of ohai and then handle the display in JS.
Could you add installation/setup instructions?
Minor typo on the header: Dashboad
Looks really nice. Was this built for Debian-based distros?
True using PHP would also have server dependant issues as well as security issues. I feel PHP is a web framework and would suggest using a application framework for this.
I think you should remove the animation on the numbers: it prevents the user from reading quickly valuable info (and isn't really useful anyway).
Still, the interface is really cool!
Very Cool. Would be nice to show Apache access logs as well (careful parsing those:).
This looks very nice!
However, multi-server support would make this even more amazing.
Pretty awesome!
Is this like a beautiful version of PHPInfo?
The interface looks very nice but no thanks, I'm not going to install PHP on my servers to have it. I'd totally set it up if it weren't for PHP. The risk is just too great to ignore.
I believe the memory assessment will always show basically no free memory due to Linux's memory management and caching. It would make more sense to subtract out the cache to see what's really used and what's just being (smartly) cached.