I'm a Drupal Association member!
Drupal 8 API tutorials
Want to learn about the Drupal 8 APIs, with worked examples? Follow my series of tutorials, covering routing, caching, entities, config and much more!
Want to hire me?
Recent blogposts
-
Altering the length of a Drupal 8 text field that contains data
Friday, July 21, 2017 - 11:31 -
A menagerie of testing: behavioural, unit, system, smoke, regression, oh my!
Friday, June 2, 2017 - 10:11 -
Including Javascript in Behat tests, all inside a headless, virtual machine
Tuesday, May 30, 2017 - 16:51
About me
I'm J-P Stacey, and I'm a freelance technical developer and software architect, working with Drupal, Javascript, Symfony, PHP and devops, with experience in project and process management and an emphasis on usability.
I live in the UK; my website is self-hosted on bigv.io; my email is hosted by Google, and that's also what I use to share files. (More info|What is this?)
This is totally true, but I
This is totally true, but I think my reply to dasjo stands: establishing a process is useful, but understanding from forensics what happened helps work out exactly what you've forgotten to do. Otherwise, you might get a PDO exception and not know what process to follow to stop it happening in future (which I think is what at least a few devs I know have been doing.)
And I absolutely agree with you re deployment, although I think tools like git - which are built to manage filesystem consistency in situ - are preferable to completely tearing down and re-uploading; unless you're using e.g. a drush-make-powered build process like Omega8/Aegir. But, yes, definitely don't just keep rsync'ing or ftp'ing code up!