Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update README.md #254

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md #254

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
20 changes: 10 additions & 10 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,8 @@ command:

The plugin hooks into the `vagrant up` and `vagrant destroy` commands
automatically.
When a machine enters or exits the running state , all active
machines with the same provider will have their `hosts` file updated
When a machine enters or exits the running state, all active
machines with the same provider will have their `/etc/hosts` file updated
accordingly. Set the `hostmanager.enabled` attribute to `true` in the
Vagrantfile to activate this behavior.

Expand Down Expand Up @@ -66,7 +66,7 @@ end

### Provisioner

Starting at version 1.5.0, `vagrant up` runs hostmanager before any provisioning occurs.
Starting with version 1.5.0, `vagrant up` runs hostmanager before any provisioning occurs.
If you would like hostmanager to run after or during your provisioning stage,
you can use hostmanager as a provisioner. This allows you to use the provisioning
order to ensure that hostmanager runs when desired. The provisioner will collect
Expand All @@ -89,14 +89,14 @@ config.vm.provision :hostmanager
Custom IP resolver
------------------

You can customize way, how host manager resolves IP address
for each machine. This might be handy in case of aws provider,
where host name is stored in ssh_info hash of each machine.
This causes generation of invalid /etc/hosts file.
You can customize how host manager resolves IP address
for each machine. This might be handy in case of the aws provider,
where host name is stored in the ssh_info hash of each machine.
This causes generation of invalid `/etc/hosts` file.

Custom IP resolver gives you oportunity to calculate IP address
for each machine by yourself, giving You also access to the machine that is
updating /etc/hosts. For example:
Custom IP resolver gives you the oportunity to calculate the IP address
for each machine by yourself, giving you also access to the machine that is
updating `/etc/hosts`. For example:

```ruby
config.hostmanager.ip_resolver = proc do |vm, resolving_vm|
Expand Down