I really think that, short of using an actual playbook that builds your prod server (or entire infrastructure) locally, this VM is now capable of doing most of what's necessary for reliable local Drupal development. Site that uses a Drush make file (configure vagrant_synced_folders and set build_from_makefile to true).Site that uses multisite for multiple domains pointing to the same docroot (configure vagrant_synced_folders, add multiple apache_vhosts with the same documentroot, and set build_from_makefile to false).Site with docroot shared from host machine (configure vagrant_synced_folders and apache_vhosts, and set build_from_makefile to false). I'd like to document how to do some of the most common setups: Were it not for their hard work and ideas, I would likely not have tidied up a lot of these niceties in time for a 4.Now that #33 has made the drupal-vm a lot more flexible (no longer does it always install a site from a makefile, you can use different kinds of Drupal sites (like sites where the entire site is in a local directory on the host, and the user installs a database), and as many as you want at the same time. I say we've, because I am extremely indebted to many consistent contributors to Drupal VM and all the upstream projects. I'm beginning some exciting experimentation using Ansible Container to build Docker images 1:1 to many of the Ansible roles I maintain, and I can't wait to share some of the optimizations I'm working on that will make Drupal VM continue to be one of the most flexible and performant development (and even production!) environments for PHP projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |