Also with the expectation that Docker for Mac Beta will become stable in the not-so-distant future, I'd like the switch to a native Docker development environment as smooth as possible. I felt that it comes with useful features that we were missing out because we were just using Vagrant's built-in Docker provider. Colleagues using PhpStorm report that mounting the Drupal root unto the host system brings the IDE to a crawl while it indexes the files.ĭocker Compose is a great tool for managing the life-cycle of Docker containers, especially if you are running multiple applications. For example, performing a grep or ag to search within files contents under Drupal 8's core takes ~10 seconds or more. Previously, we had to mount Drupal's document root to our host machine using sshfs to explore in it, but it's not exactly performant. Having toĭo this every morning when I turn on my laptop at work was no fun. I had a tough time debugging this issue, and the only resolution in sight was to do a vagrant reload - it's a time-consuming process as it rebuilds every image and running them again. Even though Vagrant's rsync-autoĬan still detect changes on the host file-system and initiates an rsync to propel files up into the containers via a mounted volume, the changes do not really appear within the containers themselves.

One issue that I keep running into when working with our development process is that the file-syncing stops working when the host machine powers off in the interim. Me to come up with an alternative process which keeps the good things we like and getting rid of/resolving the issues we encountered.įirst, I'll list some improvements that we'd like to see: Within the time-span however, we experienced a few issues here and there which led It has been working well in the several months we have used it and worked within its framework. Back in December, Tom Friedhof shared how we set up our Drupal 8 development and build process utilizing Docker.

Dockerfile for drupal hosting