[00:35] And what does ijthan use for configuration management? [00:44] It's iProprietary :-) [00:44] ChinnoDog: but, my beef with Chef is the same as my beef with Ansible or Puppet. People are using them for weird one off things [00:45] e.g. if you install gitlab, there's a command "gitlab-ctl reconfigure" [00:45] and really all that does is call chef to change some files and stuff and restarts a service [00:45] why does Chef have to do that? [00:45] Why add the bloat? [00:45] Misusing the tool isn't Chef's fault [00:46] Yeah, but I think your original statement is misuse [00:46] lol [00:46] It's a one-off thing. Just dist-upgrade :-p [00:47] if you had to configure 20 $chinnoCompy.. fine. [00:47] but 1??! [00:47] Using chef to provision a workstation isn't misuse. I can't dist-upgrade. I made a mess on here that will probably cause the upgrade to blow up. [00:47] 1 for now. Another if this one breaks. [00:48] Another if I use a different computer elsewhere [00:48] but what settings are you going to configure? [00:49] You're going to spend more time writing a cookbook than you are doing it by hand. [00:55] If it is only for one install then I agree. It is also my recovery plan if I need to start over though. e.g. laptop falls and breaks into a bazillion pieces and I need a new laptop asap. [00:55] I used to keep installation scripts for my Windows boxes too. [00:56] Hrm. I usually enjoy the idea of starting fresh when the opportunity presents itself. [11:54] ahoy [12:35] o/