{"action":"opened","issue":{"url":"https://api.github.com/repos/davidalger/devenv/issues/65","repository_url":"https://api.github.com/repos/davidalger/devenv","labels_url":"https://api.github.com/repos/davidalger/devenv/issues/65/labels{/name}","comments_url":"https://api.github.com/repos/davidalger/devenv/issues/65/comments","events_url":"https://api.github.com/repos/davidalger/devenv/issues/65/events","html_url":"https://github.com/davidalger/devenv/issues/65","id":148715046,"number":65,"title":"vhosts.sh - Cannot read file '/etc/varnish/includes.vcl'","user":{"login":"mttjohnson","id":50849,"avatar_url":"https://avatars.githubusercontent.com/u/50849?v=3","gravatar_id":"","url":"https://api.github.com/users/mttjohnson","html_url":"https://github.com/mttjohnson","followers_url":"https://api.github.com/users/mttjohnson/followers","following_url":"https://api.github.com/users/mttjohnson/following{/other_user}","gists_url":"https://api.github.com/users/mttjohnson/gists{/gist_id}","starred_url":"https://api.github.com/users/mttjohnson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mttjohnson/subscriptions","organizations_url":"https://api.github.com/users/mttjohnson/orgs","repos_url":"https://api.github.com/users/mttjohnson/repos","events_url":"https://api.github.com/users/mttjohnson/events{/privacy}","received_events_url":"https://api.github.com/users/mttjohnson/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-15T17:04:09Z","updated_at":"2016-04-15T17:04:09Z","closed_at":null,"body":"A few people have reported receiving an error message when running vhosts.sh:\r\nError message “Cannot read file '/etc/varnish/includes.vcl' (No such file or directory)\r\n('/etc/varnish/default.vcl' Line 46 Pos 9)\r\ninclude \"/etc/varnish/includes.vcl”;” after running vhosts.sh —reset-config\r\n\r\nThere is an issue with the current DevEnv where it is expecting there to be at least one .varnish.vcl file in one of your sites and would include that into the includes.vcl file... where none exist anywhere it fails to build the includes.vcl file and causes varnish to fail to restart... If you aren’t utilizing varnish it MIGHT (haven’t confirmed that) not affect anything as it should just bypass Varnish all together. \r\n\r\nAs a workaround you could probably create a mock site directory in /sites/matt-failed.dev/ and include a pub directory and a .varnish.vcl and I think it should correctly build things and spin Varnish up correctly without the errors.\r\n\r\nI hope to be patching this soon in the vhosts.sh script to create the includes.vcl file regardless as a blank file if no files are needed to be included.\r\n\r\nFuture Plans:\r\nI may have to change the architecture here of how VCL configs would work for multiple sites at some point as it doesn't seem to be all that flexible if you do need different configs for different sites."}}