Quick and easy Development Box build with Ansible and Vagrant
Explore the docs »
Report Bug
·
Request Feature
- Table of Contents
- About The Project
- Getting Started
- Usage
- Roadmap
- Contributing
- License
- Contact
- Acknowledgements
I always wanted to have a quick way to build a VM that contains all of my favorite tools and configs. Here is my take on a Dev Box build with Ansible and Vagrant.
Use it carefully.
- Vagrant
- Ruby
- Ansible
- Ansible
- Vagrant
- VirtualBox ( My preferred way for Virtualization )
- Ansible Official Installation guide
- Vagrant Official Installation guide
- VirtualBox ( My preferred way for Virtualization ) Official Installation guide
- Git Clone the repo
- cd in the cloned repo
- Run
vagrant up VM_NAME
to start and provision the instancevagrant provision VM_NAME
to re-provision the instancevagrant pause VM_NAME
to pause the instancevagrant resume VM_NAME
to resume a previously paused instancevagrant destroy VM_NAME
to completely destroy the instancevagrant ssh VM_NAME
to ssh in the instancevagrant global-status
to get all the running instances IDvagrant ssh 123abc
to ssh in the specific instance via the ID gathered earlier
If no VM_NAME is given the default VM_NAME is
Archlinux-Vagrant
Multiple VMs can be created if different VM_NAMES are given.
- VNC on browser ( Xorg Display ) - http://localhost:6081/vnc.html
- VNC on browser ( Virt Display ) - http://localhost:6081/vnc.html
- VSCode on browser - http://localhost:8080
- Ctrl - Mod key
- Ctrl+d - rofi menu
See the open issues for a list of proposed features (and known issues).
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature
) - Commit your Changes (
git commit -m 'Add some AmazingFeature'
) - Push to the Branch (
git push origin feature/AmazingFeature
) - Open a Pull Request
Distributed under the GPL-3.0 License. See LICENSE
for more information.
John Stilia - @john_stilia - [email protected]