{"action":"opened","issue":{"url":"https://api.github.com/repos/acquia/blt/issues/2067","repository_url":"https://api.github.com/repos/acquia/blt","labels_url":"https://api.github.com/repos/acquia/blt/issues/2067/labels{/name}","comments_url":"https://api.github.com/repos/acquia/blt/issues/2067/comments","events_url":"https://api.github.com/repos/acquia/blt/issues/2067/events","html_url":"https://github.com/acquia/blt/issues/2067","id":262185191,"number":2067,"title":"Improve site install experience on Acquia Cloud","user":{"login":"danepowell","id":1984514,"avatar_url":"https://avatars1.githubusercontent.com/u/1984514?v=4","gravatar_id":"","url":"https://api.github.com/users/danepowell","html_url":"https://github.com/danepowell","followers_url":"https://api.github.com/users/danepowell/followers","following_url":"https://api.github.com/users/danepowell/following{/other_user}","gists_url":"https://api.github.com/users/danepowell/gists{/gist_id}","starred_url":"https://api.github.com/users/danepowell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danepowell/subscriptions","organizations_url":"https://api.github.com/users/danepowell/orgs","repos_url":"https://api.github.com/users/danepowell/repos","events_url":"https://api.github.com/users/danepowell/events{/privacy}","received_events_url":"https://api.github.com/users/danepowell/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-10-02T18:44:11Z","updated_at":"2017-10-02T18:44:11Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"At some point, you have to install your site on AC (or other hosting environment). It doesn't seem like there's a documented best practice for how to do this.\r\n\r\nThe best method I've found is to SSH into the server and run `./vendor/bin/blt setup:drupal:install`, but this throws a bunch of warnings because of AC's read-only filesystem and file locations.\r\n\r\nWe should document the best approach, and also improve the install experience. Maybe insert some logic into those install functions to not throw so many warnings in a cloud environment.\r\n\r\nSpecifically, I see the following problems:\r\n\r\n## VM doesn't exist on Cloud\r\nLeads to errors due to missing VM:\r\n> [error]  Could not find VM. Please ensure that the VM machine name matches project.machine_name \r\n> [error]  /var/www/html/foo.prod/box/config.yml is missing. Please re-run `blt vm`.\r\n\r\n## Local settings file doesn't exist\r\n> [warning] /var/www/html/foo.prod/docroot/sites/default/settings/local.settings.php is missing.\r\n>  Do you want to generate this required settings file(s)? (y/n)\r\n\r\n## Read-only filesystem and setting permissions\r\n> [error]  Unable to set permissions for site directories."}}
{"actor":{"display_login":"danepowell"}}