Hi Jim, What I would like is a command-line process whereby I control the life-cycle of the machine (without having to jump to specific directories).
vagrant up --box bento/ubuntu14.04 --name myvm (why should a machine name be only "default"?) vagrant halt --name myvm vagrant start --name myvm vagrant destroy --name myvm vagrant ssh --name myvm -c "run a build script to build linux kernel 2.2.0" vagrant up -f Vagrantfile.X (I still want a Vagrantfile, but I don't want it limited to a particular directory, and I don't want it limited to *only* named "Vagrantfile"). Hence, my enhancement request. 1. an additional option (-f) to allow users to create vagrantfiles without having to name it Vagrantfile relieves an unnecessary restriction (one machine per directory) 2. adding an option '--box' to specify a box to create a new machine 3. option '--name' to allow users to name their machines These changes would make Vagrant more flexible. -- 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/1d1690a7-b631-41cc-8cdf-dbc9ee7d7bce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
