tldr-pages/tldr

Let's document: vagrant

Open

#18,895 opened on Oct 19, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Shell (2,507 forks)batch import
help wantedlet's documentnew command

Repository metrics

Stars
 (30,937 stars)
PR merge metrics
 (Avg merge 7d 5h) (321 merged PRs in 30d)

Description

Command description

Vagrant automates the creation and management of virtual machines. https://developer.hashicorp.com/vagrant/docs

Documentation

https://developer.hashicorp.com/vagrant/docs/cli

Platform

Common

VCS repository link (e.g. GitHub, GitLab)

https://github.com/hashicorp/vagrant

Additional information

The following subcommands are documented on a separate page: docker-exec,docker-logs, docker-run, rsync, rsync-auto https://developer.hashicorp.com/vagrant/docs/cli/non-primary

Commands

  • vagrant #371
  • vagrant box #15650
  • vagrant cloud
  • vagrant connect
  • vagrant destroy #18863
  • vagrant docker-exec
  • vagrant docker-logs
  • vagrant docker-run
  • vagrant global-status #19035
  • vagrant halt #15939
  • vagrant init #18915 #19750
  • vagrant login #18916
  • vagrant package
  • vagrant plugin #15682
  • vagrant port #19035
  • vagrant powershell
  • vagrant provision #18917
  • vagrant rdp
  • vagrant reload #18863
  • vagrant resume #18973
  • vagrant rsync
  • vagrant rsync-auto
  • vagrant share
  • vagrant snapshot #17458
  • vagrant ssh #19035
  • vagrant ssh-config #19750
  • vagrant status #18863
  • vagrant suspend #18863
  • vagrant up #18919
  • vagrant upload #18996
  • vagrant validate #15900
  • vagrant version #19001

Contributor guide

Research direction
Review the tldr pages contribution guidelines, check existing merged PRs for vagrant commands (e.g., #371, #15650), and create markdown pages for each undocumented subcommand following the established format.
Tech stack
shell
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85