Open Niwt opened 6 years ago
I would not update without backing up all databases first. Then can you update Vagrant and VirtualBox?
Also HashiCorp did a URL change without a redirect hence the 404. https://github.com/scotch-io/scotch-box/issues/367
So:
Hi Niwt
As Nick said, never update without backing up your database! As a general note: when creating an issue, please provide your version of vagrant and virtualbox. (you should keep them up to date btw.).
To update an existing environment to ScotchBox 3.5, this worked for me:
vagrand.d
Vagrant::DEFAULT_SERVER_URL.replace('https://vagrantcloud.com')
to the Vagrantfile. vagrant box add scotch/box
So, vagrant box add scotch/box
for me, was working perfectly fine and downloaded ScotchBox 3.5 from https://vagrantcloud.com/scotch/box.
Note: This will create a new VM! (which is intended)
When starting vagrant and connecting via ssh by vagrant ssh
you can check if you're on ScotchBox 3.5 with lsb_release -a
. If you see Ubuntu 16.04.2 LTS
you're on the latest (free) Version of Scotch Box :)
Note: you can also use vagrant box list
to see what versions you have installed.
Also: if you have multiple VMs, for the following ones after this first one you only have to:
vagrand.d
vagrant up
(this will create he VM)and you're good to go with a new VM running Scotch Box 3.5
First of all: Thanks for this amazing LAMP-Stack!
Using scotch box for a very long time, I'm having 10-15 projects using scotchbox 3.0. Therefore I'm having many VMs. I want to update to ScotchBox 3.5 without loosing all the databases, so I'd like to update without destroying the VMs. When following the update-article on scotch.io i get this error:
Where does this come from?
I guess re-installing vagrant/virtualbox should help right? But that means backing up 15databases etc. There should be a way to update the VMs the regular way, right?