Install New Packages With Vagrant Without Losing Your Connections
The normal vagrant reload process cause the following things to happen:
- VM is shut down
- VM is started up
- Provisioning occurs (software/packages are installed)
This is a great process because it clears everything out and resets your VM to a good state. It's a sucky process because step 1 causes SSH and other long term connections to disconnect and potentially fail.
If you use vagrant provision it only causes step 3 to occur without restarting everything. It's also much quicker when your learning how to do things with vagrant. I've spent some time the last month learning new things and it's been a real eye opener.
Scott Keck-Warren
Scott is the Director of Technology at WeCare Connect where he strives to provide solutions for his customers needs. He's the father of two and can be found most weekends working on projects around the house with his loving partner.
Top Posts
- Working With Soft Deletes in Laravel (By Example)
- Fixing CMake was unable to find a build program corresponding to "Unix Makefiles"
- Upgrading to Laravel 8.x
- Get The Count of the Number of Users in an AD Group
- Multiple Vagrant VMs in One Vagrantfile
- Fixing the "this is larger than GitHub's recommended maximum file size of 50.00 MB" error
- Changing the Directory Vagrant Stores the VMs In
- Accepting Android SDK Licenses From The OSX Command Line
- Fixing the 'Target class [config] does not exist' Error
- Using Rectangle to Manage MacOS Windows