Manually update vagrant box

If re-creating (Development-environment#re-create-guest) the vagrant guest using vagrant box update on your host will not work due to proxy or other network trouble, the following may be successful to update the vagrant box.

Download box manually

Use curl to download the box on your host. This command can be re-run to resume a download that has failed partway through.

curl --continue-at - --location --fail --show-error --output marksvc-sfdev-1.2.0.box \
  https://vagrantcloud.com/marksvc/boxes/sfdev/versions/1.2.0/providers/virtualbox/amd64/vagrant.box

Verify that the download came thru uncorrupted by doing one of the following:

In Windows, check that this command's output contains 33f4c4026107e8d85673f05c2637de0b0b405ae5a958244779ea7e91f8d09276:

certutil -hashfile marksvc-sfdev-1.2.0.box SHA256

Or in Linux,

sha256sum --check <<< "33f4c4026107e8d85673f05c2637de0b0b405ae5a958244779ea7e91f8d09276  marksvc-sfdev-1.2.0.box"

Create box metadata

Make a marksvc-sfdev-1.2.0.box.json file with content:

{
  "name": "marksvc/sfdev",
  "versions": [{
    "version": "1.2.0",
    "providers": [{
      "name": "virtualbox",
      "url": "marksvc-sfdev-1.2.0.box",
      "checksum": "33f4c4026107e8d85673f05c2637de0b0b405ae5a958244779ea7e91f8d09276",
      "checksum_type": "sha256"
    }]
  }]
}

Incorporate new box version

Run

vagrant box add marksvc/sfdev marksvc-sfdev-1.2.0.box.json

Verify by running the following, replacing ~/code/web-xforge with the path to your web-xforge repository. It should say it is the latest version, 1.2.0.

cd ~/code/web-xforge/deploy/vagrant/sfdev
vagrant box update