The OpenDevShop Homepage shows you a birds eye view of all your projects. The name, install profile, git URL, Drupal Version, and a list of all the environments are visible at a glance.
Each environment indicator is updated in realtime. You can see the status of the latest task for every site in your system.
The project dashboard shows you all the information you need about your website. Git URL, list of branches and tags, links to GitHub, links to the live environment, Drush aliases, and most importantly: your project's environments.
Each block is a running copy of your website. Name them whatever you want. Each one shows you the drupal version, the current git branch or tag, the URLs that are available, the last commit time, a files browser, and a backup system.
Under the "Environment Settings" button is a list of possible tasks:
Download Modules allows you to add drupal modules and themes to your project, automatically committing them to git.
Clone Environment creates an exact copy of your environment with a new name.
Fork Environment runs a clone, then creates a new branch with a name of your choice!
Disable & Destroy Environment. A setting prevents environments from being destroyed in two clicks, use at your discretion.
Flush all caches, Rebuild Registry, Run Cron,etc. *These tasks are not really needed if you use Deploy hooks! Cron is always enabled, and caches can be cleared on every code deployment.
Backup / Restore, as you would expect.
Run Tests allows you to manually trigger test runs.
The Deploy Code control allow you to easily change what branch or tag an environment is tracking.
Deploy Data allows you to deliver new database and files to your environment.
Deploy Stack allows you to move your environment's services (like database and files) from one server to another.
At the bottom of each environment block is a status indicator for the last task that was run on the environment.
You can click any task to view the detailed logs of any task.
DevShop is designed for developers. We want to give them exactly the information they need. No more, no less.
Out of this came the design of our task logs. We strive to make DevShop's activities as clear and transparent as possible.
After the code is deployed with git, any number of Deploy Hooks can be run.