Introducing Docman (available on github, alpha state, but used already in production environment): the Swiss Army Knife for Drupal multisite docroot management and deployment. Docman acts as a layer between your docroot – usually a git repository somewhere, but not limited to it– and multiple vendors working on different websites using your standards and predefined sets of modules.

Remember how hosting sales teams always tried to push you to buy more docroots "because otherwise it would be hard to manage websites in a Drupal multisite environment"? Docman can simplify your life so you will be able to stick to one docroot and multiple independent websites in it using the same Drupal core.

Have you ever tried to oblige different vendors to work with one Drupal core for completely different websites, inside a multisite environment, without making them break everything and with clear deployment schema? Find out how docman can make the once daunting task of multisite deployment more efficient.

Does the governance of multiple projects in one multisite environment scare you? Docman has hooks, like Drupal, to launch your tests whenever needed and for each website in multisite environment independently.

During this presentation you will peek inside the inner workings of the docman tool and see:

• All the advantages it will bring to your multisite /single doc root deployments
• A real-world case study of setting up a stable platform using this concept and the tools needed
• A development process using docman ('docman build local development' command and others)

Real-world example:

• You have a docroot at Acquia Cloud
• You have a small governance team setting up standards (Drupal core, list of contrib modules)
• You have 3 vendors working on three different websites in multisite environment