{"action":"opened","issue":{"url":"https://api.github.com/repos/geerlingguy/drupal-vm/issues/45","labels_url":"https://api.github.com/repos/geerlingguy/drupal-vm/issues/45/labels{/name}","comments_url":"https://api.github.com/repos/geerlingguy/drupal-vm/issues/45/comments","events_url":"https://api.github.com/repos/geerlingguy/drupal-vm/issues/45/events","html_url":"https://github.com/geerlingguy/drupal-vm/issues/45","id":64178940,"number":45,"title":"Document how to use drupal-vm with multisite, multiple docroots, etc.","user":{"login":"geerlingguy","id":481677,"avatar_url":"https://avatars.githubusercontent.com/u/481677?v=3","gravatar_id":"","url":"https://api.github.com/users/geerlingguy","html_url":"https://github.com/geerlingguy","followers_url":"https://api.github.com/users/geerlingguy/followers","following_url":"https://api.github.com/users/geerlingguy/following{/other_user}","gists_url":"https://api.github.com/users/geerlingguy/gists{/gist_id}","starred_url":"https://api.github.com/users/geerlingguy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/geerlingguy/subscriptions","organizations_url":"https://api.github.com/users/geerlingguy/orgs","repos_url":"https://api.github.com/users/geerlingguy/repos","events_url":"https://api.github.com/users/geerlingguy/events{/privacy}","received_events_url":"https://api.github.com/users/geerlingguy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-25T05:23:53Z","updated_at":"2015-03-25T05:23:53Z","closed_at":null,"body":"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.\r\n\r\nI'd like to document how to do some of the most common setups:\r\n\r\n  1. Site with docroot shared from host machine (configure `vagrant_synced_folders` and `apache_vhosts`, and set `build_from_makefile` to `false`).\r\n  2. 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`).\r\n  3. Site that uses a Drush make file (configure `vagrant_synced_folders` and set `build_from_makefile` to `true`).\r\n\r\nI 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. I might also need to add easier options for PHP version switching (like in acquia-cloud-vm) and add the ability to switch Ubuntu versions (should be simple enough to toggle 12.04 and 14.04 (current default)... maybe even allow switching to CentOS 6/7!)."}}