The document outlines a multisite platform using Drupal with a continuous delivery process across multiple development agencies. It discusses the server-side structure, deployment process with GitLab and Jenkins, and highlights the pros and cons of the approach. Key benefits include flexible rights management and ease of core updates, while drawbacks include fixed instance numbers and the need for manual backups.

1. Multisite platform with
continuous delivery process for
multiple development agencies
Oleksandr Linyvyi
Drupal developer @Adyax
Email: oleksandr.linyvyi@gmail.com
Twitter: @lazylinol
Drupal.org: https://drupal.org/user/984134

2. Overview
1. Requirements
2. Drupal core + subsites
3. Core updates
4. Gitlab
5. Serverside structure
6. Deployment process
7. Jenkins
8. Additional utils
9. Pros/Cons
10.Summary

4. The idea
Standard Drupal multisiting
Each subsite = separate repository
Core is common (obviously )

5. https://about.gitlab.com/features/

7. Serverside structure
3 instances
Dev
Preprod
Production
Varnish
Nginx + php-fpm
MariaDB
Memcache
SOLR

9. Deploy?
Just a simple git pull
But done by ansible playbook
Usage: ansible-playbook -i ./hosts ./project_deploy.yml -e "instance=dev project=hello version=develop"

11. Jenkins
Running code builds
Deploying code to target instances
Files/DB sync across the instances
Doing some misc stuff
in our case it is responsible for:

16. Pros
Flexible rights management in Gitlab
Easy to keep core updated
Little effort to extend (add new site)

17. Cons
Fixed instances number
Using drush for syncs/backups
Need to override core modules in certain cases

18. That’s it
Thank you!