5093f3120e
This is a big commit, and I apologize in advance for the future
git-blames all pointing to me. This commit does a few things:
1. Merges the website/docs and website/www repo into a single website repo
to be in line with other HashiCorp projects
2. Updates to use middleman-hashicorp
3. Converts less to scss to be in line with other projects
4. Updates page styles to be in line with other projects
5. Optimizes images
6. Prepare for S3 + Fastly deployment with scripts, etc.
7. Removes blog posts (they have been transferred to hashicorp.com with
redirects in place
8. Updated sitemap generation script for better SEO
9. Fixed many broken links
10. Add description to all fields
1.4 KiB
1.4 KiB
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| docs | Upgrading Vagrant | installation-upgrading | If you are upgrading from Vagrant 1.0.x, please read the specific page dedicated to that. This page covers upgrading Vagrant in general during the 1.x series. |
Upgrading Vagrant
If you are upgrading from Vagrant 1.0.x, please read the specific page dedicated to that. This page covers upgrading Vagrant in general during the 1.x series.
Vagrant upgrades during the 1.x release series are straightforward:
- Download the new package
- Install it over the existing package
The installers will properly overwrite and remove old files. It is recommended that no other Vagrant processes are running during the upgrade process.
Note that Vagrantfile stability for the new Vagrantfile syntax is not promised until 2.0 final. So while Vagrantfiles made for 1.0.x will continue to work, newer Vagrantfiles may have backwards incompatible changes until 2.0 final.
Run into troubles upgrading? Please
report an issue
if you run into problems upgrading. Upgrades are meant to be a smooth
process and we consider it a bug if it was not.