A session about the evolution of deployment process from FTP to config management, GIT workflows and automation from Drupal Dev Days Seville. Originally held at Drupal Mountain Camp in Davos.
• Open your favourite FTP client • Replace files on server with your updated PHP • Hit F5 in your browser • Life is good! Deployment before life became complicated
http://www.mysite.com/login.php?user=admin&pass=admin Warning: fopen(/../users-and-passwords.txt) [function.fopen]: failed to open stream. No such file or directory in /home/ my_site/public_html/login.php on line 56 Warning: stream_get_contents() expects parameter 1 to be resource, boolean given in /home/my_site/public_html/ login.php on line 57 Warning: fclose() supplied argument is not a valid stream resource in /home/my_site/public_html/login.php on line 58
Revision Control 1982 RCS (Revision Control System ) 1986 CVS (Concurrent Version System ) 1989 Sir Tim Berners-Lee invents W eb 2005 Git 2011 Git @ drupal.org 2001 Drupal release
Git • It replaced well established FTP workflows. • It introduced new and strange commands and concepts. • Due to steep learning curve, only a fraction of it was used.
Why is it an Antipattern? • Power of Git lies in branching • Publicly accessible .git directory is a serious security risk • SSH to server for every single pull? • Boring task that can easily be automated!
Things to Consider • Post-receive hook can do much more than simply copying the working tree. • Control access to repositories. • Multiple sites on a single server, all owned by git, all run by apache user is not a good idea. 23
Why is it an Antipattern? • it is just time consuming and boring! • The need for inline code commenting. • 100’s comments in issue queue. • There are some better tools for that, such as Gerrit, Github or Gitlab
diff --git a/CHANGELOG.txt b/CHANGELOG.txt index 4853101..c015fb4 100644 --- a/CHANGELOG.txt +++ b/CHANGELOG.txt @@ -1,4 +1,53 @@ +Drupal 7.54, 2017-02-01 +----------------------- +- Modules are now able to define theme engines (API ad + https://www.drupal.org/node/2826480). +- Logging of searches can now be disabled (new option + interface). +- Added menu tree render structure to (pre-)process ho theme_menu_tree() + (API addition: https://www.drupal.org/node/2827134). +- Added new function for determining whether an HTTPS + (API addition: https://www.drupal.org/node/2824590). +- Fixed incorrect default value for short and medium d + type configuration page. +- File validation error message is now removed after s valid + file. +- Numerous bug fixes. +- Numerous API documentation improvements. +- Additional performance improvements. +- Additional automated test coverage. + +Drupal 7.53, 2016-12-07 +----------------------- +- Fixed drag and drop support on newer Chrome/IE 11+ v update + when jQuery is updated to 1.7-1.11.0. + +Drupal 7.52, 2016-11-16 Meanwhile in Planet Drupal • Somebody updated core from 7.50 to 7.54 • 4501 lines of diff • Impossible to review • Entire git history soon becomes clogged and useless after a dozen of core+module updates.
Meanwhile in Planet Drupal Patching (hacking) core and contrib Make a change in core/contrib Maintain a list of hacked files Never perform an update again Make a patch file Commit the patch file Maintain a list of patches Update a module git apply -v name_of.patch
Drush make • Built to be a packaging tool • …but became a patching tool • Downloads Drupal core, modules and themes from d.o. • Downloads libraries in .tar.gz or .zip format • Fetches and applies patches
Things to Consider • Prepare a backup strategy if things go wrong. • Running drush make on live server can and will result in site instability. • Drush make does not install Drupal or contrib modules. • Drush make does not run database update. • Drush make does not handle dependencies.
Composer isn’t Drush • Does not do patching. • Not aware of Drupal’s directory structure. • Drupal.org has its own package repository. • There’s some new syntax to be learned. • Not a speed champion!
The fuss of setting up the project Getting the core composer create-project drupal/drupal my-d8-site 8.2.* Wait for 131 seconds in average 0 35 70 105 140 Drush Composer (warm caches) Composer (cold caches) 131s 31s 12s
The fuss of setting up the project Setting the right repository composer config repositories.drupal composer https://packages.drupal.org/8 "repositories": { "drupal": { "type": "composer", "url": "https://packages.drupal.org/8" } }
The fuss of setting up the project Making sure modules are downloaded to appropriate folders "extra": { "installer-paths": { "modules/contrib/{$name}": ["type:drupal-module"], "profiles/contrib/{$name}": ["type:drupal-profile"], "themes/contrib/{$name}": ["type:drupal-theme"] } } "require": { "composer/installers": "^1.0.20" }
Composer template for Drupal projects composer create-project drupal-composer/drupal-project • Installs Drupal in web directory • Uses composer-generated autoloader • Ships with functional .gitignore file • Composer-patches installed and set up • Composer set up to respect Drupal directory structure • Creates default writable versions of settings.php, services.yml and sites/ default/files directory • Installs drush and drupal console locally
It’s not all lollipops and unicorns! • Auto-increment indexes in Drupal 7 • Crazy terminology: recreate, revert? • A feature is just a module, let’s build some custom logic in it! • Circular dependency between features • Disable a feature, see what will happen… • WE DO NOT HAVE ANYTHING BETTER IN D7 :(
The need to compile the front end • Growing number of tools, including CSS compiling, JavaScript compiling, asset management, image optimisation etc. • Setting up local development stacks and keeping the toolset same across the large team can be challenging. • Should front end be compiled locally and then committed, or vice versa?
A really simple D7 deploy script #!/usr/bin/env bash cd /var/www drush -y make project.make drush -y updatedb drush cc all drush -y features-revert-all grunt build
git push Local Web host push event Let’s make it complicated cd /var/www composer install drush -y updatedb drush cache-rebuild drush -y config-import grunt build
Git push Assemble container Run build hook Stop serving requests Replace container Run deploy hook Serve requests Site instability during builds Serve requests from the old container until the new one was built.
Matter of security Strong isolation of services on network, read only file system for PHP files, regular updates, minimum OS, single point of password access
Matter of scaling Every environment is a cluster. Commit YAML files to git repository to add or remove services, or use web UI to request more resources
bbujisic
shinmiy
tmokmss
little_rubyist
kinocoboy2
katsyoshi
horie1024
stewemetal
akitotsukahara
microcms
shoheihosaka
numeroanddev
yui_knk
myddelton
jeffersonlam
mthomps
eitanlees
destraynor
kneath
lemiorhan
cassininazir
sferik
tmm1
cromwellryan
lara