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.8 KiB
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| docs | Vagrant Share | share | Vagrant Share allows you to share your Vagrant environment with anyone in the world, enabling collaboration directly in your Vagrant environment in almost any network environment with just a single command- "vagrant share". |
Vagrant Share
Vagrant Share allows you to share your Vagrant environment with anyone in
the world, enabling collaboration directly in your Vagrant environment
in almost any network environment with just a single command:
vagrant share.
Vagrant share has three primary modes or features. These features are not mutually exclusive, meaning that any combination of them can be active at any given time:
-
HTTP sharing will create a URL that you can give to anyone. This URL will route directly into your Vagrant environment. The person using this URL does not need Vagrant installed, so it can be shared with anyone. This is useful for testing webhooks or showing your work to clients, teammates, managers, etc.
-
SSH sharing will allow instant SSH access to your Vagrant environment by anyone by running
vagrant connect --sshon the remote side. This is useful for pair programming, debugging ops problems, etc. -
General sharing allows anyone to access any exposed port of your Vagrant environment by running
vagrant connecton the remote side. This is useful if the remote side wants to access your Vagrant environment as if it were a computer on the LAN.
The details of each are covered in their specific section in the sidebar to the left. We also have a section where we go into detail about the security implications of this feature.
Vagrant Share requires an account with HashiCorp's Atlas to be used.