This project is not covered by Drupal’s security advisory policy.

Site Actions/Home Tab
Server Health Tab
Database Performance Tab
Caching Performance Tab
Storage Health Tab
Backup Manager Tab
Authenticated Users Now Online Tab
Session Browser
Broadcast Manager Tab

SiteCommander is an interactive dashboard to manage and monitor your Drupal 8 site. It features a variety of shortcuts and visuals to help you quickly gauge things or perform routine tasks.

NOTE: While fully functional at this time, this module is still in development, and should be considered in a beta state.

SiteCommander features include:

  • Implemented as a Drupal block, so you can put it on the same page as other blocks to make your own dashboard
  • Breakdown of published nodes by type, with shortcuts to create new nodes, or browse nodes by type
  • Full featured Backup Manager with 1-click backup/restore, backup scheduler, retention strategy, backup mirroring
  • Live Broadcast Manager, which allows you to broadcast realtime growl messages to your current site visitors
  • Quickly see how many modules you have installed and a shortcut to install new ones
  • Quickly see how many authenticated users and visitors are currently online (and view a list of them)
  • Quickly browse active sessions (by user) and optionally terminate them
  • Quickly see today's top site searches
  • See when cron last ran and a shortcut to manually run it
  • Integration with Redis for stats, ability to clear Redis cache
  • Integration with PHP Opcache for stats, ability to clear Opcache
  • Integration with APC for stats, ability to clear APC cache
  • CPU load average gauges, so you can monitor your server's workload
  • View health of all attached storage devices (utilization %)
  • See when the updates checker last ran, and a shortcut to manually check for updates
  • Shortcut to clear/rebuild the Drupal cache
  • Shortcut to clear out old aggregated CSS/JS files that just take up space
  • See how much disk space your full Drupal install is taking up
  • Integration with the MailChimp module to see some high level statistics about your lists, subscribers, open rates, and click through rates.
  • Tabbed interface for ease of navigation
  • More to come!


Known Issues

  • Certain functionality, such as CPU Load Averages, currently only works in Linux environments. Support for Windoze servers is on the roadmap.
  • Currently, this module works best when the environment is running only ONE (1) Drupal server. If you are running multiple Drupal servers in a load-balanced configuration, please keep in mind that only limited testing has been done in such environments. Feedback and testing help is appreciated!
  • Certain parts of the look/feel are going to depend on your theme, which means your install may not look like these screenshots. We are working on making the CSS more encapsulated to provide a more consistent experience.

Installation Instructions

  1. Download and install the module (./modules/custom/sitecommander)
  2. Run an update with Drush to pull in dependencies: "drush up" (Be sure to have the Composer Manager module installed!)
  3. Configure it either on the modules page, or via admin/config/sitecommander
  4. Create a new page (e.g. /system-status), and add the Site Commander block to it. It is a full-width block, so put it in the main content area, etc.
  5. Be sure to restrict access to the new page to admins only or what not.
  6. Many of the icons on the page are interactive, so click on them to add new nodes, put the system in maintenance mode, etc.


Again, to configure, click the gears icon on your SiteCommander page, go to the configuration page and look for SiteCommander, or just navigate to /admin/config/sitecommander.

General Settings

Exclude Specific Content Types From Dashboard

Select the content types that would like to exclude from appearing on the dashboard. Currently, this only affects the "Content Items By Type" widget.

Include Bootstrap CSS via CDN

SiteCommander uses the most-awesome Bootstrap CSS framework. If you have a theme that is based on Bootstrap, you won't need to check this box. If you already have a theme using Bootstrap, and you check this box, it will still work, but modals will disappear as soon as they appear. Also, there is no reason for an extra page request, so disable it if you are already using it elsewhere!

Include jQuery via CDN

Most people, if not everyone, won't need to check this, but if for some bizarre reason, you aren't using jQuery in Drupal, check this box.

Dashboard AJAX Refresh Rate (in seconds)

Most of the SiteCommander statistics will refresh automatically/periodically. Just provide some sensible value here. We recommend the default, which is every 60 seconds, but edit to taste.

Tag Cloud Widget Settings

Name of the Taxonomy Vocabulary to Use in the Tag Cloud Widget

By default, SiteCommander will use the "tags" vocabulary to generate the tag cloud. However, you are free to specify whatever vocabulary you wish. The only caveat is that the terms in the vocabulary actually be tied to content types.

Restrict the Tag Cloud to This Many Entries

This simply limits the tag cloud to a certain number of terms (important if you have a boat load of terms in your vocabulary!).

Starting Color for Tags (Smallest Frequency)

Pretty self-explanatory. Terms with the lowest number of occurrences in the tag cloud will start out at this color.

Ending Color for Tags (Largest Frequency)

Terms with the largest number of occurrences will end up with this color. Terms will be shaded to some color between the starting color and ending color, again, depending on how often they are used/seen.

Redis Settings

Redis can be used as both a backend cache for Drupal, as well as a mechanism to allow SiteCommander to track how many visitors are on your site. We highly recommend it! If you need help setting up, we even wrote an article to help you!

Redis Hostname

For most folks, this can simply be "localhost", if you are running Redis on the same physical server as Drupal. Of course, you can specify whatever hostname Redis is running on if it is deployed elsewhere.

Redis Port

This is the TCP/IP port that Redis is listening on. The default is 6379, and for most folks, this will be fine.

Redis Database to Use

Redis gives you sixteen (16) databases or "buckets" to use. When in doubt, just pick a number between 0 and 15. But for more advanced Redis users, you may want to isolate Drupal/SiteCommander's use of Redis to a particular bucket, since when we tend to take an "all or nothing" approach to flushing it when you request us to do so! You don't want to inadvertently lose data from other apps.

Anonymous User Tracking

As mentioned previously, SiteCommander can track the number of visitors to your site. There are two ways we can do this. The first, is by using Redis. In this case, what we do is add a Redis entry for each visitor (by IP address). Those entries are kept for a configurable amount of time. The problem with this is obvious. We simply count up how many of these entries are in Redis to determine the number of visitors. The visitor may very well have moved on, but there entry in Redis hasn't yet expired.

The second, and more accurate method, is by using Pusher (see for more info). By using Pusher, the statistics are realtime. If a user has one of your pages open, he/she will be counted as a visitor. Visit to set up your free (or paid) account. Most sites can probably get away with a free account. We highly recommend this service, however. It's uses are endless! Please note that in order to use Pusher with SiteCommander, you will need to also install our pusher_integration module!

Server Pool

This is currently unused, but will be used in the future. For now, feel free to just plop the name of your host in there (or "localhost" for most smaller sites with just one Drupal app server).

Backup Manager Settings

SiteCommander can use "drush" (required) to create and restore backup images for you. Install drush if you haven't already - it's worth it!

Backup Directory

This is the path where SiteCommander will store backup image files. For larger sites, we highly recommend you have a separate storage host/device to store your backups. Simply mount the remote share using SAMBA/SMBCLIENT/etc. to your Drupal server. That way, if something actually happens to your Drupal host(s), your backups aren't lost!

Path to drush

Self-explanatory. This is the full path/filename to your drush executable. The default is /usr/local/bin/drush.

Max Backup Age (in Days)

Again, pretty straightforward. Backups older than this value, in days, will be periodically pruned/removed to save space. The default is seven (7) days.

Enable Scheduled Backups

SiteCommander can perform scheduled backups for you. What's great about this, is the backups are performed in the background via Drupal cron, so they won't tie up your system.

Minimum Number of Hours Between Backups

Whenever visitors visit your site, Drupal cron kicks off to see if there are any tasks it needs to perform. SiteCommander will not run another scheduled backup until *at least* this many hours has passed since the last backup was created. The default is 24.

Enable Mirroring Backup Files to a Remote Host

For data redundancy, we recommend mirroring your scheduled backups to a remote host. Again, if something happens to your local Drupal host, you don't want to lose your backup files!

Interface to Use For Mirroring Backup Files to a Remote Host

Currently, only sftp is supported.

Remote Port #

The remote port # to use. By default, this is 22 for sftp.

Remote Mirror Host

The hostname of the remote host that sftp will connect to for mirroring backups.

Remote Directory

The full path, on the remote host, where you want to store your mirrored backup files.

Remote Username

The username to use when remotely connecting to your mirror host.

Remote Password

The password for the above user.

Broadcast Manager Settings

SiteCommander features a really cool tool called Broadcast Manager which enables you to send realtime "growl"-like messages to current site visitors. To enable, simply use the checkbox. Note: this requires that you have our pusher_integration module installed, as well as an account (free or paid) at

Supporting organizations: 
Paid for development

Project information