Hi,
A more lightweight approach would be to distribute a default Vagrantfile
and ask users to put it in their ~/.vagrant.d/ directory
You could enable / disable your company specific defaults with an env var
for example
Cheers,
Torben
Am 10.10.2014 01:57 schrieb Chris Chalstrom
I'm working on a plugin to be used for simplifying the process of deploying
to my org's environment. As part of this, I'd like to package some default
configuration that would typically go into the Vagrantfile into my plugin.
My goals are to allow anyone to use my plugin OR standard vagrant
