Torben, this has hugely cleared things up for me, thank you :-) As for the ARGV[2] parsing: the docker provider is a bit of a special case > as it is usually not configured with a basebox, but you still can provide > working docker baseboxes: > https://github.com/tknerr/vagrant-docker-baseimages > > (no fedora docker boxes in there yet, but pull requests welcome ;-)) >
This makes a lot more sense now, depending on how we end up handling the Docker projects I may well be contributing Fedora boxes. > [...] > That being said, if it really comes to representing different environments > (like local/ci/staging/prod) I personally choose to have a subdirectories > with it's own Vagrantfile each, especially if it's a multi-vm Vagrantfile > describing a whole stack rather than a single vm > For most of our projects we're only dealing with single VMs (for standardisation of dev environment more than anything) that deploy to containers in production, but separating out multiple Vagrantfiles makes complete sense for the more complex ones. Thanks again Torben, your pointers have been a great help. Regards, Ben. -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/373e0f3c-f917-4c9f-bc43-5e676935215b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
