Open-Awesome
CategoriesAlternativesStacksSelf-HostedExplore
Open-Awesome

© 2026 Open-Awesome. Curated for the developer elite.

TermsPrivacyAboutGitHubRSS
  1. Home
  2. Vagrant
  3. vagrant-hostsupdater

vagrant-hostsupdater

MITRuby1.2.4

A Vagrant plugin that automatically manages /etc/hosts entries for your development VMs.

GitHubGitHub
1.2k stars128 forks0 contributors

What is vagrant-hostsupdater?

Vagrant Hostsupdater is a Ruby gem plugin for Vagrant that automatically updates the host machine's `/etc/hosts` file. It maps hostnames to the IP addresses of Vagrant virtual machines, solving the problem of manually editing hosts files for local development environments.

Target Audience

Developers and DevOps engineers using Vagrant for local development who need seamless hostname resolution for their virtual machines without manual configuration.

Value Proposition

It eliminates the tedious manual editing of hosts files, automates the process across Vagrant lifecycle commands, and supports advanced configurations like multiple network adapters and cloud providers.

Overview

Vagrant Hostsupdater is a plugin for Vagrant that automatically adds and removes entries in the host system's /etc/hosts file. It simplifies local development by mapping hostnames to the IP addresses of Vagrant virtual machines, eliminating the need for manual hosts file edits.

Key Features

  • Automatic Hosts Management — Adds entries on vagrant up, resume, and reload, and removes them on halt, destroy, and suspend.
  • Alias Support — Allows defining multiple hostname aliases for a single IP address.
  • Multiple Network Adapters — Supports mapping specific hostnames to different private network IPs using a hash configuration.
  • Skip Option — Enables skipping hosts updates for specific network configurations with a hostsupdater: "skip" flag.
  • Privilege Escalation Control — Provides instructions for suppressing sudo/UAC prompts on Linux, macOS, and Windows.
  • Cloud Provider Integration — Includes support for AWS and Google Cloud providers, detecting public IPs from instance tags or names.

Philosophy

It aims to streamline the development workflow by automating a repetitive manual task, ensuring that hostname resolution works seamlessly across Vagrant environments.

Use Cases

Best For

  • Automating hosts file updates for Vagrant development environments
  • Managing multiple hostname aliases for a single Vagrant VM
  • Configuring complex Vagrant setups with multiple private network adapters
  • Integrating Vagrant VMs with AWS or Google Cloud providers
  • Suppressing sudo/UAC prompts for hosts file edits on Linux, macOS, or Windows
  • Skipping hosts updates for specific network configurations in Vagrant

Not Ideal For

  • Projects starting after 2021 that require ongoing maintenance and compatibility with newer Vagrant versions
  • Teams prioritizing security updates and bug fixes in development tooling
  • Environments heavily using modern containerization (e.g., Docker) instead of Vagrant
  • Developers unfamiliar with system administration tasks like editing sudoers files

Pros & Cons

Pros

Seamless Hosts Automation

Automatically adds and removes entries on Vagrant commands like up, halt, and destroy, eliminating the need for manual edits to /etc/hosts as described in the README.

Flexible Alias Configuration

Supports multiple hostname aliases per IP and hash-based mapping for multiple private network adapters, allowing precise control over hostname resolution in complex setups.

Cloud Provider Integration

Includes support for AWS and Google Cloud providers, detecting public IPs from instance tags or names, though it requires external CLI tools like AWS CLI.

Privilege Control Options

Provides detailed instructions for suppressing sudo/UAC prompts on Linux, macOS, and Windows, reducing interruption during development workflows.

Cons

Abandoned Project

The maintainer explicitly declared it not maintained in March 2021, meaning no updates, bug fixes, or support for newer Vagrant versions or operating systems.

Complex Sudoers Setup

Requires manual editing of system files like /etc/sudoers.d on Linux/macOS or using cacls on Windows, which is error-prone and poses security risks if misconfigured.

External Tool Dependencies

For cloud features, it depends on AWS CLI or Google Cloud SDK, adding setup overhead and potential compatibility issues in automated environments.

Frequently Asked Questions

Quick Stats

Stars1,152
Forks128
Contributors0
Open Issues35
Last commit4 years ago
CreatedSince 2013

Tags

#devops#ruby-gem#virtual-machines#vagrant-plugin#local-development#development-tools#automation

Built With

R
Ruby

Included in

Vagrant622
Auto-fetched 10 hours ago

Related Projects

saharasahara

a plugin for vagrant that allows you manage a sandbox state

Stars731
Forks51
Last commit6 years ago
vagrant-scpvagrant-scp

Copy files to a Vagrant VM via SCP.

Stars314
Forks31
Last commit4 years ago
vagrant-host-shellvagrant-host-shell

simple vagrant provisioner that executes commands on the host

Stars112
Forks17
Last commit9 years ago
vagrant-ansible-localvagrant-ansible-local

Vagrant plugin that provision your VM with ansible playbooks directly from the guest VM

Stars64
Forks5
Last commit11 years ago
Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a projectStar on GitHub