There's nothing worse then stopping over at a colleagues desk to help them with an issue and ending up at
- "Well, apache/mysql/php is working on my local"
- "I would investigate this with xdebug, do you have that setup?"
- "Yeah you'll need php5 to work on Site A and 7.1 to work on Site B, I'll slack you the blog post I used to set them up side by side"
With a standard local development environment across your team statements like the above occur much less frequently. Agreeing to a standard across a team is always a challenge, and always comes with benefits and drawbacks. At Digital Bridge the dev team has successfully standardized our local development around a customzied DrupalVM that's increased access to development tooling while also reducing local setup times. During the session we'll cover
- the high level benefits and drawbacks to using DrupalVM over other local tooling solutions
- the assumptions that were made about our clients and dev team
- the changes we've seen within our team as the standard was adopted
- how we manage issues, documentation, and rolling out updates across the team
- the customizations we've made to DrupalVM
At the end of the session attendees should have a grasp of the considerations that were made when choosing our standard, the various benefits and tradeoffs that our local development approach offers, and a rough idea on how to technically implement a similar DrupalVM setup.