These are chat archives for fgrehm/vagrant-cachier

17th
Dec 2014
Michael K
@Yserz
Dec 17 2014 03:35
ohai, I observed that vagrant-cachier is not caching chef files...do i have to set up special commands to activate the chef-caching?
something like config.omnibus.cache_packages = true in Vagrantfile or cache_type 'BasicFile' in knife.rb?
Michael K
@Yserz
Dec 17 2014 03:44
one example of a package which is not cached is the chef-server from the chef-server cookbook on centos 6.6. Surprisingly the packge is present in the cache of the host machine (.vagrant.d) but is never taken in the vm :/
Michael K
@Yserz
Dec 17 2014 03:49
Vagrant 1.7.1, vagrant-cachier (1.1.0), vagrant-omnibus (1.4.1) (installing chef 12.0.0)
Fabio Rehm
@fgrehm
Dec 17 2014 13:24
Sorry, I haven't used omnibus in a looong time =/
Michael K
@Yserz
Dec 17 2014 13:28
rly? no more chef or what's ur workflow?
Fabio Rehm
@fgrehm
Dec 17 2014 14:41
started using ansible not long ago, but I havent been messing up with servers for a while now so I dont need for a proper provisioning tool these days. http://fgrehm.viewdocs.io/devstep is what I've been using on my daily work (which borrows lots of ideas from vagrant-cachier's caching approach)
Michael K
@Yserz
Dec 17 2014 18:57
just started reading...but looks like docker is behind that, right? :)
confirmed ;D
Fabio Rehm
@fgrehm
Dec 17 2014 23:44
Right now: yes. For the future: its just a set of heroku buildpacks, so in theory it could be easily applied to some vagrant provisioner plugin
https://gitter.im/fgrehm/devstep if someone is interested on discussing that :)