-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Caching bigger downloads on the host machine would speed up rebuild times for the vm #21
Comments
Thoughts on adding the |
I like the idea of the script downloading stuff, but then caching it between machine rebuilds. I don't think we want to keep our own copy of the binaries. |
Welp, it looks like we can't even do it!
So, I guess we're good to go with b3ec9b4 closing the ticket. If that's the case, I'll let @lo5an decide since he created the issue. |
There is also the possibility of:
|
...and we should probably add |
Maybe a vagrant plugin like https://github.com/fgrehm/vagrant-cachier would be better for caching system packages? Updated to expand: I've only been using vagrant-cachier for a week or so, but it's been working well so far, and I like that it handles more than just .debs. It seems to be a reasonably active project, and it's nice and modular, so we could recommend that people use it without making it a dependency. I've got the vagrant-cachier config in a Vagrantfile in my lookup path so that it applies to all of my vagrant vms. |
That said, caching OS packages is definitely beyond the scope of what I was originally thinking, so I'm happy to mark this as closed and create a new issue for package caching :-) |
Saving bigger downloads in a cache in the mounted /vagrant folder would speed up subsequent rebuild times.
The text was updated successfully, but these errors were encountered: