Closed ivomarino closed 7 years ago
actually when running appflow vagrant reload atlantis instead of appflow vm reload atlantis we get this:
appflow vagrant reload atlantis
appflow vm reload atlantis
mkdir -p ~/Downloads/Software mkdir -p ~/Downloads/Software/Vagrant-Boxes cd ~/Downloads/Software/Vagrant-Boxes && wget -c http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box && mv trusty-server-cloudimg-amd64-vagrant-disk1.box trusty64.box && cd ~/Documents/webdev/appflow --2017-01-11 11:13:54-- http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box Resolving cloud-images.ubuntu.com...
we should avoid this in order to break things, so maybe appflow vagrant should be an alias for appflow vm.
appflow vagrant
appflow vm
As suggested, now you control the VMs with appflow vagrant <command>
appflow vagrant <command>
To initialize a VM appflow init-vm A small tool will ask the distro you want
appflow init-vm
actually when running
appflow vagrant reload atlantis
instead ofappflow vm reload atlantis
we get this:we should avoid this in order to break things, so maybe
appflow vagrant
should be an alias forappflow vm
.