{"action":"created","issue":{"url":"https://api.github.com/repos/laravel/framework/issues/6531","labels_url":"https://api.github.com/repos/laravel/framework/issues/6531/labels{/name}","comments_url":"https://api.github.com/repos/laravel/framework/issues/6531/comments","events_url":"https://api.github.com/repos/laravel/framework/issues/6531/events","html_url":"https://github.com/laravel/framework/issues/6531","id":50444331,"number":6531,"title":"Allow per-project installations for Homestead 2","user":{"login":"joshuajabbour","id":66879,"avatar_url":"https://avatars.githubusercontent.com/u/66879?v=3","gravatar_id":"","url":"https://api.github.com/users/joshuajabbour","html_url":"https://github.com/joshuajabbour","followers_url":"https://api.github.com/users/joshuajabbour/followers","following_url":"https://api.github.com/users/joshuajabbour/following{/other_user}","gists_url":"https://api.github.com/users/joshuajabbour/gists{/gist_id}","starred_url":"https://api.github.com/users/joshuajabbour/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joshuajabbour/subscriptions","organizations_url":"https://api.github.com/users/joshuajabbour/orgs","repos_url":"https://api.github.com/users/joshuajabbour/repos","events_url":"https://api.github.com/users/joshuajabbour/events{/privacy}","received_events_url":"https://api.github.com/users/joshuajabbour/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/laravel/framework/labels/proposal","name":"proposal","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":25,"created_at":"2014-11-30T02:19:39Z","updated_at":"2015-03-03T02:29:00Z","closed_at":null,"body":"With the rewrite of Homestead v2, it is now considerably more difficult (if not impossible) to share development environment code on a project. One of the key benefits of Vagrant is committing the `Vagrantfile` to a repository and thereby having all developers working from the same environment. (Isn't that the whole point of Vagrant?) But with Homestead 2, all your config lives in your own personal `~/.homestead` directory, and is non-shareable. \r\n\r\nI was never really a fan of the instructions for Homestead 1 which advocated using a single, central clone of the homestead repository. (Am I really the only one who uses separate homestead boxes per project? Do other people prefer not to segregate environments? That's like developing on our own little shared hosting boxes, allowing different project code and installation requirements to co-mingle.) But at least with the original Homestead it was possible to put the homestead files inside your project's repo (I used `subtree add`, since I'd customize the provision scripts.) With Homestead 2 and `after.sh`, the ability to customize the environment is getting better (and somewhat more reproducible), but taking a huge step backwards in shareability.\r\n\r\nWhile bundling homestead commands as a composer project is great, further centralizing config seems to be taking Homestead in a wrong direction..."},"comment":{"url":"https://api.github.com/repos/laravel/framework/issues/comments/76875325","html_url":"https://github.com/laravel/framework/issues/6531#issuecomment-76875325","issue_url":"https://api.github.com/repos/laravel/framework/issues/6531","id":76875325,"user":{"login":"ThatTomPerson","id":1112472,"avatar_url":"https://avatars.githubusercontent.com/u/1112472?v=3","gravatar_id":"","url":"https://api.github.com/users/ThatTomPerson","html_url":"https://github.com/ThatTomPerson","followers_url":"https://api.github.com/users/ThatTomPerson/followers","following_url":"https://api.github.com/users/ThatTomPerson/following{/other_user}","gists_url":"https://api.github.com/users/ThatTomPerson/gists{/gist_id}","starred_url":"https://api.github.com/users/ThatTomPerson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ThatTomPerson/subscriptions","organizations_url":"https://api.github.com/users/ThatTomPerson/orgs","repos_url":"https://api.github.com/users/ThatTomPerson/repos","events_url":"https://api.github.com/users/ThatTomPerson/events{/privacy}","received_events_url":"https://api.github.com/users/ThatTomPerson/received_events","type":"User","site_admin":false},"created_at":"2015-03-03T02:29:00Z","updated_at":"2015-03-03T02:29:00Z","body":"I'm not saying you cant use homestead\r\nI'm working in a group of 3, so homestead wouldn't work for us because if one person makes a change  like installs Mongo how do you handle that??\r\n\r\nhomestead as it is, does not handle stuff like this,\r\nso I made some changes to homestead and just copy them into the root of my project\r\nyou can see my changes at https://github.com/ThatTomPerson/homestead\r\n\r\nthis is more customisable and all configuration is now in the repo\r\nif you want mongodb on your vm just write a create-mongo.sh in the scripts and change homestead.rb to run it\r\n\r\nI have no idea who you would get homestead to do this"}}