Drush
Workflow
Power
About Me
Ron Northcutt
@rlnorthcutt
About JR
- Springboard Platform
- Large non-profit clients
- Emilys List, ASPCA, Rescue.org, IFAW
Now Hiring!
Do good work helping support good causes.
Work from home with an amazing team.
Which Monkey?
Managing code
GIT
Managing Everything else
DB & Files Manual option
- track down server creds
- mysql dump
- scp sql file
- scrub sql (insert scary stories)
- import
- ignore files or rsync
- reset dev environment
- time : way too long
slow, error prone, dangerous, scary
Everything Else take 2
DB & Files Drush option
$> drush sync-site
time : MUCH faster
safer, more secure, easier, betterer
files : sync-files OR stage_file_proxy
What you need
- drush server aliases : $> drush @prod cc all
- structure/skip tables array : (note on wildcards)
- drush command aliases : so this
$> drush sql-dump --structure-tables-key=common+springboard --skip-tables-key=common
-- becomes --
$> drush get-db - custom drush commands : $> drush go-local
- settings.php adjustment : store dev/staging/prod settings in the repo, but still hide local
where to get it
Overview and explanation
Github repo
http://github.com/JacksonRiver/sb-drush-workflow
Look at the code
HOMEWORK
- Find a project that needs better workflow
- Get & customize the drush setup
- Get & customize the settings files
- Commit to your repo
- Use drush like a pro
Bonus
Teach someone else
Questions?
Drush Workflow
By Ron Northcutt
Drush Workflow
- 2,429