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.
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!
REQUIREMENTS:
- Drupal 8.x
- PHP 5.5 or higher (untested under PHP 7)
- Drush installed
- Composer Manager Module
- ssh2 module for PHP (optional, but needed for backup mirroring functionality)
NOTE: 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, it is highly recommended that you wait until we complete the multi-server support functionality.
NOTE: Right now, the latest code can always be found on GitHub (not the master branch, but the 8.x-1.x-dev branch). It is sync'd back to here periodically until the project gets approved as a full project.
Company Project Page: http://incurs.us/open-source-projects/sitecommander
GitHub: https://github.com/IncursusInc/sitecommander/tree/8.x-1.x-dev
Project Page: https://www.drupal.org/sandbox/incursus/2772735
Git Clone Command: git clone --branch 8.x-1.x-dev https://git.drupal.org/sandbox/incursus/2772735.git sitecommander
Comments
Comment #2
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpsgitdrupalorgsandboxincursus2772735git
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #3
incursus commentedHave made tweaks to address the paraview suggestions that made sense. The rest either do not (e.g. calling \Drupal::xxx methods in a static function), are false positives, or result from formatting issues with third party (license-compliant) files.
Comment #4
incursus commentedComment #5
incursus commentedComment #6
incursus commentedComment #7
incursus commentedComment #8
incursus commentedComment #9
incursus commentedComment #10
incursus commentedComment #11
incursus commentedComment #12
incursus commentedComment #13
hesnvabr commentedThis module enabled successfully and fulfilled all the conditions.
Comment #14
incursus commentedComment #15
incursus commentedComment #16
incursus commentedComment #17
incursus commentedComment #18
incursus commentedComment #19
incursus commentedComment #20
incursus commentedComment #21
incursus commentedComment #22
incursus commentedComment #23
incursus commentedComment #24
incursus commentedComment #25
incursus commentedI've been steadily committing code to this project while it is waiting to be approved - just a heads up. Lots of new features have been added over the past few weeks.
Comment #26
incursus commentedJust a quick note regarding the review bonus. I honestly don't feel that I am qualified to provide a code review against someone else's module, much less three of them. Given that I am very much on the early side of the D8 learning curve. Just a FWIW.
Edit: I should add that I hope to be in a position at some point to provide more help with reviewing stuff. But right now, I'm just not there.
Comment #27
incursus commentedComment #28
incursus commentedJust commited some updated files which addressed a couple hundred minor annoyances reported by Paraview. The rest are either false positives, or silly formatting things about spaces, etc., which I do not plan on addressing.
Comment #29
incursus commentedComment #30
PA robot commentedProject 1: https://www.drupal.org/node/2782259
Project 2: https://www.drupal.org/node/2773107
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #31
avpaderno