Update docs to properly name Vagrant Cloud
This commit is contained in:
parent
a7b228eb69
commit
5817cef233
|
@ -6,11 +6,11 @@ sidebar_current: "vagrant-cloud-boxes-catalog"
|
|||
|
||||
# Discovering Vagrant Boxes
|
||||
|
||||
Vagrant Enterprise serves a public, searchable index of Vagrant boxes. It's easy to find
|
||||
Vagrant Cloud serves a public, searchable index of Vagrant boxes. It's easy to find
|
||||
boxes you can use with Vagrant that contain the technologies you need
|
||||
for a Vagrant environment.
|
||||
|
||||
You don't need a Vagrant Enterprise account to use public boxes.
|
||||
You don't need a Vagrant Cloud account to use public boxes.
|
||||
|
||||
1. Go to the [Box search page](https://vagrantcloud.com/boxes/search)
|
||||
|
||||
|
@ -37,10 +37,10 @@ are some things to note when you're choosing a box:
|
|||
trust the box more than an anonymous user
|
||||
- __The number of downloads of the box__. Heavily downloaded boxes
|
||||
are likely vetted more often by other members of the community. Hashicorp
|
||||
responds to reports of malicious software distributed via Vagrant Enterprise
|
||||
responds to reports of malicious software distributed via Vagrant Cloud
|
||||
and takes down boxes
|
||||
- __The latest release date__. More up-to-date boxes contain up-to-date
|
||||
software
|
||||
- __Availability of the box download__. Vagrant Enterprise periodically checks if box
|
||||
- __Availability of the box download__. Vagrant Cloud periodically checks if box
|
||||
has is publicly accessible. You can see this information on the box
|
||||
page next to the provider
|
||||
|
|
|
@ -6,27 +6,27 @@ sidebar_current: "vagrant-cloud-boxes-create-x"
|
|||
|
||||
# Creating a New Vagrant Box
|
||||
|
||||
This page will cover creating a new box in Vagrant Enterprise and how to distribute
|
||||
it to users. Boxes can be distributed without Vagrant Enterprise, but
|
||||
This page will cover creating a new box in Vagrant Cloud and how to distribute
|
||||
it to users. Boxes can be distributed without Vagrant Cloud, but
|
||||
miss out on several [important features](/docs/vagrant-cloud/boxes).
|
||||
|
||||
There are __three ways to create and upload Vagrant Boxes to Vagrant Enterprise__. All
|
||||
There are __three ways to create and upload Vagrant Boxes to Vagrant Cloud__. All
|
||||
three options are outlined below.
|
||||
|
||||
We recommend using Packer, as is it is fully repeatable and keeps a strong
|
||||
history of changes within Vagrant Enterprise. However, for some situations, including
|
||||
history of changes within Vagrant Cloud. However, for some situations, including
|
||||
legacy workflows, the Web UI or API will work well.
|
||||
|
||||
All three options require you [sign up for Vagrant Enterprise](https://vagrantcloud.com/account/new).
|
||||
All three options require you [sign up for Vagrant Cloud](https://vagrantcloud.com/account/new).
|
||||
|
||||
## Creating Boxes with Packer
|
||||
|
||||
Using Packer requires more up front effort, but the repeatable and
|
||||
automated builds will end any manual management of boxes. Additionally,
|
||||
all boxes will be stored and served from Vagrant Enterprise, keeping a history along
|
||||
all boxes will be stored and served from Vagrant Cloud, keeping a history along
|
||||
the way.
|
||||
|
||||
## Creating Boxes via the Vagrant Enterprise Web Interface
|
||||
## Creating Boxes via the Vagrant Cloud Web Interface
|
||||
|
||||
You'll first need to create a box file. This can be done via
|
||||
the [vagrant `package` command](http://docs.vagrantup.com/v2/boxes/base.html)
|
||||
|
@ -47,7 +47,7 @@ locally in Vagrant. `virtualbox` is the most common provider.
|
|||
1. Upload the `.box` file for each provider, or use a url to the `.box`
|
||||
file that is publicly accessible
|
||||
|
||||
You can find all of your boxes in the [Vagrant section](https://vagrantcloud.com/vagrant) of Vagrant Enterprise.
|
||||
You can find all of your boxes in the [Vagrant section](https://vagrantcloud.com/vagrant) of Vagrant Cloud.
|
||||
|
||||
Once you've created and released a box, you can release new versions of
|
||||
the box by clicking "Create New Version" under the versions sidebar on
|
||||
|
|
|
@ -7,16 +7,16 @@ sidebar_current: "vagrant-cloud-boxes-distributing"
|
|||
## Distributing Boxes
|
||||
|
||||
To distribute the box to your team, update your Vagrantfile to reference the
|
||||
box on Vagrant Enterprise.
|
||||
box on Vagrant Cloud.
|
||||
|
||||
Vagrant.configure(2) do |config|
|
||||
config.vm.box = "username/example-box"
|
||||
end
|
||||
|
||||
Now when a team member runs `vagrant up`, the box will be downloaded from Vagrant Enterprise.
|
||||
Now when a team member runs `vagrant up`, the box will be downloaded from Vagrant Cloud.
|
||||
If the box is private, the team member will be prompted to authorize access. Users
|
||||
are granted access to private resources by logging in with a Vagrant Enterprise username and
|
||||
password or by using a shared Vagrant Enterprise token.
|
||||
are granted access to private resources by logging in with a Vagrant Cloud username and
|
||||
password or by using a shared Vagrant Cloud token.
|
||||
[Learn more about authorization options here](/docs/vagrant-cloud/users/authentication.html).
|
||||
|
||||
## Private Boxes
|
||||
|
@ -43,7 +43,7 @@ and if necessary a collaborator can be removed
|
|||
### Vagrant Login
|
||||
|
||||
In order to access these private boxes from Vagrant, you'll need to first
|
||||
authenticate with your Vagrant Enterprise account.
|
||||
authenticate with your Vagrant Cloud account.
|
||||
|
||||
1. Run `vagrant login`
|
||||
2. Enter your credentials
|
||||
|
|
|
@ -16,14 +16,14 @@ Boxes support versioning so that members of your team using Vagrant can update
|
|||
the underlying box easily, and the people who create boxes can push fixes and
|
||||
communicate these fixes efficiently.
|
||||
|
||||
Vagrant Enterprise makes it easy to manage the versioning of boxes. Versioning boxes in
|
||||
Vagrant Enterprise allows for easy updates, transparent fixes, and clear communication in
|
||||
Vagrant Cloud makes it easy to manage the versioning of boxes. Versioning boxes in
|
||||
Vagrant Cloud allows for easy updates, transparent fixes, and clear communication in
|
||||
changes made. Learn more about the [box release lifecycle
|
||||
here](/docs/vagrant-cloud/boxes/lifecycle.html).
|
||||
|
||||
## Vagrant Box Catalog and Discovery
|
||||
|
||||
Vagrant Enterprise hosts a catalog of publically available Vagrant Boxes. These are boxes
|
||||
Vagrant Cloud hosts a catalog of publically available Vagrant Boxes. These are boxes
|
||||
created by both HashiCorp and community contributions. You can find an owner of
|
||||
a box by selecting their username in the URL or on the box page.
|
||||
|
||||
|
|
|
@ -30,7 +30,7 @@ user will see the following message in Vagrant:
|
|||
|
||||
## Box Version Release States
|
||||
|
||||
Vagrant Enterprise lets you create new versions of boxes without
|
||||
Vagrant Cloud lets you create new versions of boxes without
|
||||
releasing them or without Vagrant seeing the update. This lets you prepare
|
||||
a box for release slowly. Box versions have three states:
|
||||
|
||||
|
|
|
@ -28,7 +28,7 @@ things they cannot do are:
|
|||
## Vagrant Login
|
||||
|
||||
In order to access these boxes from Vagrant, you'll need to first
|
||||
authenticate with your Vagrant Enterprise account.
|
||||
authenticate with your Vagrant Cloud account.
|
||||
|
||||
1. Run `vagrant login`
|
||||
2. Enter your credentials
|
||||
|
|
|
@ -7,8 +7,8 @@ sidebar_current: "vagrant-cloud-boxes-release-workflow"
|
|||
# API Release Workflow
|
||||
|
||||
Creating new boxes through their [release lifecycle](/docs/vagrant-cloud/boxes/lifecycle.html)
|
||||
is possible through the Vagrant Enterprise website, but you can also automate
|
||||
the task via the Vagrant Enterprise API.
|
||||
is possible through the Vagrant Cloud website, but you can also automate
|
||||
the task via the Vagrant Cloud API.
|
||||
|
||||
1. Create box, or locate a boxes `tag`, like `hashicorp/precise64`
|
||||
2. After some event, like the end of a CI build, you may want to
|
||||
|
|
|
@ -6,7 +6,7 @@ sidebar_current: "vagrant-cloud-boxes-using"
|
|||
|
||||
# Finding and Using Boxes
|
||||
|
||||
A primary use case of Vagrant Enterprise by HashiCorp is to be able to easily find
|
||||
A primary use case of Vagrant Cloud by HashiCorp is to be able to easily find
|
||||
boxes you can use with Vagrant that contain the technologies you need
|
||||
for a Vagrant environment. We've made it extremely easy to do that:
|
||||
|
||||
|
|
|
@ -1,12 +1,12 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Vagrant Enterprise"
|
||||
page_title: "Vagrant Cloud"
|
||||
sidebar_current: "vagrant-cloud"
|
||||
---
|
||||
|
||||
# Vagrant Enterprise
|
||||
# Vagrant Cloud
|
||||
|
||||
Vagrant Enterprise provides the following features for Vagrant:
|
||||
Vagrant Cloud provides the following features for Vagrant:
|
||||
|
||||
- [Vagrant Box Catalog](/docs/vagrant-cloud/boxes/catalog.html)
|
||||
- [Vagrant Box Creation](/docs/vagrant-cloud/boxes/create.html)
|
||||
|
|
|
@ -21,7 +21,7 @@ interface until they enable it or leave the organization.
|
|||
Visit your organization's configuration page to enable this feature. All
|
||||
organization owners must have two-factor authentication enabled to require the
|
||||
practice organization-wide. Note: locked-out users are still be able to interact
|
||||
with Vagrant Enterprise using their `ATLAS_TOKEN`.
|
||||
with Vagrant Cloud using their `ATLAS_TOKEN`.
|
||||
|
||||
## Disabling Two-Factor Authentication Requirement
|
||||
|
||||
|
|
|
@ -1,12 +1,12 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_page_title: "Organizations in Vagrant Enterprise"
|
||||
page_page_title: "Organizations in Vagrant Cloud"
|
||||
sidebar_current: "vagrant-cloud-organizations"
|
||||
---
|
||||
|
||||
## Organizations in Vagrant Enterprise
|
||||
## Organizations in Vagrant Cloud
|
||||
|
||||
Organizations are a group of users in Vagrant Enterprise that have access and
|
||||
Organizations are a group of users in Vagrant Cloud that have access and
|
||||
ownership over shared resources. When operating within a team, we recommend
|
||||
creating an organization to manage access control, auditing, billing and
|
||||
authorization.
|
||||
|
|
|
@ -1,12 +1,12 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Vagrant Enterprise Support"
|
||||
page_title: "Vagrant Cloud Support"
|
||||
sidebar_current: "vagrant-cloud-support"
|
||||
---
|
||||
|
||||
# Contacting Support
|
||||
|
||||
All users of Vagrant Enterprise are urged to email feedback, questions or
|
||||
All users of Vagrant Cloud are urged to email feedback, questions or
|
||||
requests to the HashiCorp team.
|
||||
|
||||
### Free Support
|
||||
|
@ -17,8 +17,8 @@ hours.
|
|||
|
||||
## HashiCorp Tools Support
|
||||
|
||||
It's often the case that Vagrant Enterprise questions or feedback relates to
|
||||
the HashiCorp tooling. We encourage all Vagrant Enterprise users to search for
|
||||
It's often the case that Vagrant Cloud questions or feedback relates to
|
||||
the HashiCorp tooling. We encourage all Vagrant Cloud users to search for
|
||||
related issues and problems in the open source repositories and mailing lists
|
||||
prior to contacting us to help make our support more efficient and to help
|
||||
resolve problems faster.
|
||||
|
@ -28,7 +28,7 @@ websites.
|
|||
|
||||
## Documentation Feedback
|
||||
|
||||
Due to the dynamic nature of Vagrant Enterprise and the broad set of features
|
||||
Due to the dynamic nature of Vagrant Cloud and the broad set of features
|
||||
it provides, there may be information lacking in the documentation.
|
||||
|
||||
In this case, we appreciate any feedback to be emailed to us so
|
||||
|
|
|
@ -6,13 +6,13 @@ sidebar_current: "vagrant-cloud-users-authentication"
|
|||
|
||||
# Authentication
|
||||
|
||||
Vagrant Enterprise requires a username and password to sign up and login.
|
||||
Vagrant Cloud requires a username and password to sign up and login.
|
||||
However, there are several ways to authenticate with your account.
|
||||
|
||||
### Authentication Tokens
|
||||
|
||||
Authentication tokens are keys used to access your account via tools or over the
|
||||
various APIs used in Vagrant Enterprise.
|
||||
various APIs used in Vagrant Cloud.
|
||||
|
||||
You can create new tokens in the token section of your account settings. It's
|
||||
important to keep tokens secure, as they are essentially a password and can be
|
||||
|
|
|
@ -6,6 +6,6 @@ sidebar_current: "vagrant-cloud-users"
|
|||
|
||||
# User Accounts
|
||||
|
||||
Users are the main identity system in Vagrant Enterprise. A user can be a
|
||||
Users are the main identity system in Vagrant Cloud. A user can be a
|
||||
member of multiple [organizations](/docs/vagrant-cloud/organizations/index.html),
|
||||
as well as individually collaborate on various resources.
|
||||
|
|
|
@ -6,7 +6,7 @@ sidebar_current: "vagrant-cloud-users-recovery"
|
|||
|
||||
# Account Recovery
|
||||
|
||||
If you have lost access to your Vagrant Enterprise account, use the reset
|
||||
If you have lost access to your Vagrant Cloud account, use the reset
|
||||
password form on the login page to send yourself a link to reset your password.
|
||||
|
||||
If an email is unknown, [contact us](mailto:support@hashicorp.com) for further
|
||||
|
|
Loading…
Reference in New Issue