Hill Country A & B
Your mission, should you choose to accept it: deploy a enterprise-class content management solution that runs entirely on your existing web server environment, supports multiple sites, maintains existing user access, security, and disk quota protections, is easy for non-technical contributors to learn and use while being flexible enough to handle a wide range of sites, and is relatively simple for IT to maintain--while still being expected to do your day-to-day job functions, as well. All of this, of course, is expected on a budget of zero. While this may sound like the plot of a sci-fi thriller, it is the very real challenge presented to a team of five IT and Publications staff at RIT two years ago. After polling contributors on the options they'd expect from a CMS offering and convening a group of developers from across our campus community to evaluate several options, we decided that Drupal would best fit our needs and started down the long, bumpy road to deployment. Despite many technical hurdles, project members leaving the university mid-way through the project, and many late nights and weekends, our team was successful. This session will demonstrate the final approach we took to achieve our goal--including our unique configurations, custom module development, and automation tools--while discussing the problems and pitfalls we encountered along the way. We'll also look at management, performance, and scalability enhancements that we are considering as part of a "phase two" of the project. Anyone looking to deploy Drupal, or any content management system for that matter, should attend to learn from our successes...and our frustrations. ----------- If this session is chosen for the TPR track, I'd like to request session TPR3. John knows why. :) To help classify this presentation, it will focus mainly on the technical details of deploying Drupal, including server architecture, Apache configuration, and module development.