Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Vagrant Virtual Development Environment Cookbook

You're reading from   Vagrant Virtual Development Environment Cookbook 35 solutions to help you utilize virtualization with Vagrant more effectively – learn how to develop and manage Vagrant in the cloud to improve collaboration

Arrow left icon
Product type Paperback
Published in Feb 2015
Publisher
ISBN-13 9781784393748
Length 250 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Chad O Thompson Chad O Thompson
Author Profile Icon Chad O Thompson
Chad O Thompson
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Vagrant Virtual Development Environment Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Setting Up Your Environment FREE CHAPTER 2. Single Machine Environments 3. Provisioning a Vagrant Environment 4. Provisioning with Configuration Management Tools 5. Networked Vagrant Environments 6. Vagrant in the Cloud 7. Packaging Vagrant Boxes Vagrant Plugins A Puppet Development Environment Using Docker with Vagrant Index

Sharing folders with rsync


Sharing files and folders with Vagrant machines is a typical use of Vagrant in a development environment. Files on a host machine can be shared with a running Vagrant machine, giving developers the advantage of being able to execute code in a production-like environment while having the ability to use desktop productivity tools (IDEs and text editors) to modify code. There are some cases where sharing folders between a host and a guest might not be possible, or might not perform well for the task at hand.

Two possible examples are:

  • Processes that generate significant disk activity (I/O) on shared folders: Hypervisor folder sharing (particularly VirtualBox) can cause Vagrant processes to become I/O bound. Using NFS can help, but might not always be available. (Exporting NFS shares require root access to the host machine and in a few cases, it might not be available at all.)

  • Vagrant can be used to control virtual machines in remote locations (even in remote data...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images