You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running multiple vagrant stacks with pe_build I end up eating through disk space because I've extracted the same tarball multiple times in different directories.
The tarballs are downloaded centrally in ~/vagrant.d/pe_builds and, IMO, should be extracted centrally as well so all vagrant stacks can use the same installers instead of duplicating effort.
The text was updated successfully, but these errors were encountered:
Could be possible. Although, then we'd have to symlink into each environment in order to run installations from the /vagrant mount. And Windows has opinions on that.
When running multiple vagrant stacks with pe_build I end up eating through disk space because I've extracted the same tarball multiple times in different directories.
The tarballs are downloaded centrally in
~/vagrant.d/pe_builds
and, IMO, should be extracted centrally as well so all vagrant stacks can use the same installers instead of duplicating effort.The text was updated successfully, but these errors were encountered: