Show HN: Vagrantfile for every language – Looking for contributors

Have you considered just using one base vagrant file and using remote scripts for each language?<p>eg: config.vm.provision &#x27;shell&#x27;, path: &#x27;<a href="https://raw.githubusercontent.com/adlawson/vagrantfiles/master/elixir/latest.sh&#x27;" rel="nofollow">https:&#x2F;&#x2F;raw.githubusercontent.com&#x2F;adlawson&#x2F;vagrantfiles&#x2F;mast...</a><p>I am a big fan of super simple provisioning for vagrant boxes. For development and trying new things a simple bash script has proven, in my experience, to be much less of a headache then chef etc.

(OP) I&#x27;ve been maintaining this repository of language Vagrantfiles for a while now, but I&#x27;d like to see the number of supported langs and number of active maintainers increase.<p>I think that one of the most difficult barriers to trying out a new language is the initial setup. Some sites like golang.org and haskell.org let you play around on the homepage, but it isn&#x27;t quite the same as having a working local environment.<p>Anyway, thanks for any support you may offer.

I was just doing this [0], but with boxes instead of provision scripts. I was going the script way but it bit me when I was without internet for a while. Arguably your approach is better because people can see exactly what packages you are installing.<p>[0]: <a href="https://bitbucket.org/breb/vagrant-boxes" rel="nofollow">https:&#x2F;&#x2F;bitbucket.org&#x2F;breb&#x2F;vagrant-boxes</a>

Kind of neat, from the Simplest Thing That Could Possibly Work perspective.<p>(Sometimes all you need is five lines of shell script to provision something, vs a full blown provisioning system and all the scaffolding that implies)

I was thinking of doing something like this too - looks like you beat me to it. Will be happy to contribute - I&#x27;ll hit you up on Github.