Thank you! This should do it.
On Wednesday, February 11, 2015 at 10:15:50 PM UTC-8, Torben Knerr wrote: > > Yes you can! > > Just put a .vagrantplugins file next to your Vagrantfile, see this comment > here: > https://github.com/mitchellh/vagrant/issues/3775#issuecomment-60338968 > > That shipped with 1.7.0 I believe > > Cheers, Torben > Am 12.02.2015 03:12 schrieb <[email protected] <javascript:>>: > >> Hi, >> >> I'm trying to extend Vagrant with additional commands and use its plugin >> system for this. I do not want to release the plugin in any form because >> it's only useful for what I'm working on. >> >> I'd like to include plugin's source in my repository and simply load the >> plugin from its latest source, without even building a gem. I also don't >> want to use `bundle exec vagrant` outside of development of the plugin but >> instead use a system-wide stable Vagrant. >> >> Is this possible? I know that most of Vagrant's functionality is based on >> plugins. How does Vagrant load its internal plugins? >> >> Thanks, >> Juliusz >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
