1.
Code Driven
Development in Drupal
ANDRIY YUN
Drupal developer, Skilld

2.
Processes & Workflow

3.
DB Driven Development

4.
Something’s wrong, but what?

5.
Productivity after few years

6.
The Goal
Development workflow
+
Stable processes of delivery
of new features for customer
-
Human factor and systematic errors

7.
Deployment to prod by one click

8.
Ability to scale project team

9.
Code Driven
Development

10.
What should be moved to code?
- Entity types & fields
- Panels and pages
- Roles & Permissions
- Variables
- Initial content (nodes, taxonomy terms, etc)
Use just the exportable friendly modules
- Views
- Image styles
- Text formats
- Rules

11.
How to use Features module
MANUALS
- Bundling site settings using Features https://goo.gl/aijPJT
- Configuration Management with Features http://goo.gl/gat3X7
VIDEO TUTORIALS
- Intorduction to Features module https://goo.gl/Jr13O5
- Drupal Features Module https://goo.gl/OQ69TW
- Strongarm module https://goo.gl/z519Wz

12.
Workflow environments
Local environments
Git repository storage (e.g. GitHub/GitLab)
Integration evironment
Build script

13.
Project lifecycle
from scratch

14.
INITIAL STEPS
- drush dl drupal
- copy/paste minimal -> custom
- add base set of modules
BUILD
drush site-install custom Integration
environment
Local
environment
Profile based way

15.
pre install actions
- git pull
- delete content file and caches
drop db
drush site install
post install actions
- upload translations
- import content
- frontend build processes
Profile build script
building process
building process

16.
Project lifecycle
after first release

17.
SQL based way
prod_db.sql
git pull
drush updb
git pull
drush updbhook_update_N
custom_deployment.install

18.
pre update actions
- git pull
drop current db
upload db from prod
drush updb
post update actions
- registry rebuild
- frontend processes
- clear cache
SQL build script
prod_db.sql
building process
building process

19.
prod_db.sql
Local dev
envs
Integration
Stage
Prelive
Prod
Code review
Builds history
Tests
Sniffers
Linters
building process
CodeDrivenDevelopment workflow
building process

20.
Typical issues

21.
Using equal environments
Prod = Stage = Integration = Local dev

22.
Code review inside the team
Developers do code review for each other
- Use common approaches for features
- Knowledge exchange inside the team
- Better quality of code
- Increase responsibility for review code

23.
DB manage approach
Use always latest prod db
Preparing prod db for use in development
Daily db backup script from prod
All enviroments should use sinle DB

24.
Profits after using
CodeDrivenWorkflow
Fix errors on early phase
Reduce time for bugfixing
Minimizing the impact of the human factor
Simplified everyday deployment

25.
Deployment to prod with Code Driven Development

26.
Continuous Integration
tools for Drupal

27.
Cloud solutions

28.
Self installation solutions
CIbox
https://github.com/propeoplemd/cibox
DrupalCI
https://www.drupal.org/project/drupalci
Code Driven Starter Kit
https://bitbucket.org/deweb-studio/code-driven-starter.kit

29.
Andriy Yun, Kyiv
e-mail: andriy.yun@gmail.com
d.org: drupal.org/u/andriyun
skype: c_cluber
Any questions?