Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

One more argument for a heavyweight core: Vagrant is perfect for delivering a configured environment to designers and less-experienced developers. But once you start tacking on plugin installation to an already burdensome process (download VirtualBox, download Vagrant, launch Terminal, find the directory, run vagrant up), you lose the 'vagrant up'-and-done quality.

As it stands, your options for plugin installation are:

1) Instruct your users to 'vagrant plugin install XXX' in your README. Hope that they get the right versions.

2) Use "bindler," a now-deprecated plugin manager for Vagrant. That's:'vagrant plugin install bindler', then 'vagrant bindler setup', and finally a 'vagrant plugin install' to auto-install the packages you specify in a JSON file.

Neither very attractive options.

If Vagrant could get support for a plugin manager in core, then I'm all for plugins. I have dreams of 'vagrant up' reading plugin requirements from your Vagrantfile and automatically installing them into that environment only. (@mitchellh? ;) But for now the monolithic core model seems to be working quite well.

--

Anyway, so much fun stuff in this release! Particularly psyched about box versioning and the rsync shared folders—two features I've hackily implemented myself in shell scripts on top of Vagrant 1.3 for work.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: