# devopsgroup-io/vagrant-hostmanager

:pencil: A Vagrant plugin that manages hosts files within a multi-machine environment.

Repository: https://github.com/devopsgroup-io/vagrant-hostmanager
Canonical: https://ross.abutalabs.com/products/vagrant-hostmanager
Language: Ruby
License: MPL-2.0
License Family: copyleft
Topics: vagrant-plugin, hosts, hostsfile, dns, development-environment, virtual-machine
Last push: 2023-07-30T19:48:52+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 4907, "days_push": 1130, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1464, forks 142 (observed 2026-08-28T04:04:47.872112+00:00)

## What it is
A Vagrant plugin that automatically manages the hosts file on guest machines and optionally the host machine. It enables hostname resolution in multi-machine Vagrant environments where IP addresses are not known in advance, such as cloud-provider deployments.

## Use cases
- manage hosts files across multiple vagrant machines
- resolve hostnames between vagrant guest machines
- automatically update hosts file on vagrant up and destroy
- enable name resolution for multi-machine vagrant environments with dynamic IPs
- add hostname aliases for vagrant boxes
- keep host machine hosts file in sync with vagrant guests

## When to choose
- you run multi-machine Vagrant environments where machines need to reach each other by hostname
- you deploy Vagrant boxes to cloud providers where IP addresses are assigned dynamically
- you want hosts file updates automated on vagrant up/destroy instead of editing files manually
- you need both guest and host hosts file management with configurable aliases

## When to avoid
- you use Docker Compose or Kubernetes, which provide built-in service discovery
- you run a single Vagrant machine and can hardcode its IP in your hosts file
- you need DNS management beyond local hosts files
- your project has moved from Vagrant to other tooling

## Facets
- artifact type: plugin
- maturity: maintenance
- function: configuration-management, networking, developer-tools, cli
- domain: developer-tools, networking
- platform: cross-platform, cli
- tags: vagrant-plugin, hosts-file, dns, multi-machine, development-environment, virtual-machine, ruby, devops, virtualization

## Member repositories
- devopsgroup-io/vagrant-hostmanager (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:47.872112+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:35:09.754671+00:00, confidence not recorded.
  - readme: https://github.com/devopsgroup-io/vagrant-hostmanager (fetched 2026-08-28T04:04:47.872112+00:00, sha f77947370161)
- Data as of 2026-08-30T08:39:29.467469+00:00.