Standardizing a development environment with Docker is challenging for a variety of reasons, the most common being that Docker simply is not the best of friends with Windows; particularly versions before Windows 10. Regardless, when you’re running a modern development team with engineers and designers who have varying preferences of workstation, your environment needs to support them all. In the past, we used Vagrant + Virtualbox + Ansible to build a virtual machine and we went from there. These days using Docker we can support an even deeper level of abstraction where you can run the environment natively, or in scenarios like Windows or on remote servers for demo purposes…
Tired of the permission errors with your cache/logs in a Vagrant environment? Me too! After being mildly annoyed with having to manually delete /var/cache and /var/logs repeatedly during “local” development, I decided to brut force matters into my own hands and solve this little annoyance once and for all. Ironically, Symfony 3.3 is addressing some of this, so it may be obsolete by then, but in the meantime… What are we doing here? Define cache and logs directories for a specific environment. Wouldn’t it be awesome if we could customize these as parameters in the FrameworkBundle? Yes, yes it would! Write a simple CacheCommand that overrides the default cache:clear PARTY!!!! Customize your getCacheDir and getLogDir methods by…
If you’re experiencing a fatal error when loading a Vagrant machine, chances are you just need to upgrade your version of Vagrant. Specifically this error, when using ubuntu/xenial (Ubuntu 16.04 LTS)
/sbin/ifdown eth1 2> /dev/null
Upgrade your local install of Vagrant to at least 1.8.5 and you’ll be set.