Not all modules belong on Drupal.org
Over time Stanford Web Services has built a large library of custom modules, features, and themes. Some of the work made its way back to Drupal.org, but some of it is specific to Stanford or higher education types. You can find most of this work on our GitHub organization page as we like to be open source. Not only do we share our code with the Stanford community...we share with the whole Drupal community. Anyone and everyone can download and use the things we build.
Sometimes the things we build have bugs and need to be updated. A problem with our features and custom modules is that they don't have an update status like those available from Drupal.org. Some folks have asked us "Why don't you run a features server" to support update status? The reason is that we like to work with GitHub, and it provides us and our developers many tools that a features server does not have. The good news is that GitHub has an API and a release system. This allowed us to create a module to get update status information from GitHub into Drupal.
We called it ERUS
You can find ERUS on the project page of Drupal.org or on our GitHub account. ERUS stands for External Repository Update Status. With this module, and a line in your module's .info file, you can get information about release status for your custom modules and themes right in Drupal. This has proven valuable for us as more and more teams across our campus adopt and use our shared work. We don't know where our work will end up next and cannot expect those who install our modules to follow our GitHub pages. Using this module, they can get the update information they need right in their website.
How it works
- Pick one of your features or custom modules on GitHub. It has to be in its own repository like: https://github.com/SU-SWS/stanford_bean_types
- Add `project status url` to the .info file of the module that is the full url to the GitHub page. Look at this example.
- Set the version number to something that conforms to the Drupal 7 version naming scheme, e.g.: 7.x-1.0-dev or 7.x-1.1
- Create a new release via GitHub's release system using the same name as the version.
- Download and enable the ERUS module in your Drupal site.
- (optional) If the repository is private you will need to enter a GitHub username and password that can read from the repository.
- Visit the update status page in your Drupal site to see the versions.
You can also use Drush to view and update the modules.
For more information on the installation, configuration, and extension of this module, please visit: https://github.com/SU-SWS/erus and https://github.com/SU-SWS/erus/blob/7.x-1.x-dev/plugins/README.md
Example of ERUS in action
Thanks to Zach Chandler and Brian Wood for their contributions to this project.