A LIGHT-WEIGHT DEVOPS
APPROACH TO ISLANDORA
Twitter: @DataG
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 United States
License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/us/
or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California,
94105, USA. Other rights are available; please contact the author for more information.
Technical Drivers
• Self-contained directory
• Easily replicate developer, staging and
production environments
• Track and contribute to upstream
development
• Put configuration under version control
• Support multi-site setup
One-directory Setup
• Extensive use of Git Submodules for Drupal,
Islandora, etc.
• Relative symbolic links within the directory
• Configuration files generated by scripts
Inside the Box (Source)
• Fedora Commons
• Drupal
• Islandora
• GSearch configuration
• Site-specific configuration, modules, themes
Inside the Box (Binaries)
• Tomcat
• Adore Djatoka
• SOLR
• FITS
Outside the Box
• Apache HTTPD
• MySQL RDBMS
• Java JVM
• ImageMagic
• Poppler Utils
• Ghostscript
• Tesseract
Git Submodules
• Adds a git repository inside another
• Top-level repository tracks the commit ID of
the submodule
Drupal Features
• Stores module dependancies, variables,
permission roles, etc.
• Updated by script-driven value substitutions
Demonstrations
• Adding a new Islandora module
• Pushing configurations to staging
• Keeping up-to-date (monitoring upstream)
• Creating a new site
To-Dos
• http://github.com/lyrasis/reposervice
• Continue to refactor out LYRASIS-specific
names, variables, etc.
• Refactor bin/reposervice-config out of bash
• Code a helper script for adding a submodule
• If there is interest, generalize and fork to
http://github.com/Islandora

A Light-weight DevOps Approach to Islandora

  • 1.
    A LIGHT-WEIGHT DEVOPS APPROACHTO ISLANDORA Twitter: @DataG This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/us/ or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA. Other rights are available; please contact the author for more information.
  • 2.
    Technical Drivers • Self-containeddirectory • Easily replicate developer, staging and production environments • Track and contribute to upstream development • Put configuration under version control • Support multi-site setup
  • 3.
    One-directory Setup • Extensiveuse of Git Submodules for Drupal, Islandora, etc. • Relative symbolic links within the directory • Configuration files generated by scripts
  • 4.
    Inside the Box(Source) • Fedora Commons • Drupal • Islandora • GSearch configuration • Site-specific configuration, modules, themes
  • 5.
    Inside the Box(Binaries) • Tomcat • Adore Djatoka • SOLR • FITS
  • 6.
    Outside the Box •Apache HTTPD • MySQL RDBMS • Java JVM • ImageMagic • Poppler Utils • Ghostscript • Tesseract
  • 7.
    Git Submodules • Addsa git repository inside another • Top-level repository tracks the commit ID of the submodule
  • 8.
    Drupal Features • Storesmodule dependancies, variables, permission roles, etc. • Updated by script-driven value substitutions
  • 9.
    Demonstrations • Adding anew Islandora module • Pushing configurations to staging • Keeping up-to-date (monitoring upstream) • Creating a new site
  • 10.
    To-Dos • http://github.com/lyrasis/reposervice • Continueto refactor out LYRASIS-specific names, variables, etc. • Refactor bin/reposervice-config out of bash • Code a helper script for adding a submodule • If there is interest, generalize and fork to http://github.com/Islandora