41–45 of 45 posts
I am using Github's Boxen, which works quite well https://boxen.github.com/
boxen looked nice to me, but I really wanted to avoid puppet (even if I never tried, it's often compared to chef and I have lots of bad experiences with chef !)
Although they are both configuration management tools, they are different.
What kind of issues did you have with chef? And when?
Earlier quoted context omitted.
because writing yaml is way easier than writing a bash script.
This yaml approach requires me to know a lot more about existing software than the bash script does. I will need to: - Read up on the documentation for osxc or battle school - Look at other configuration files to get a feel for what mine needs to look like. - Learn about the differences between playbooks or recepies or what have you. - Download some proprietary software that I will likely never use again. This is all…
I would rather use Ansible. It seemed like it would fit what I'm trying to do, but everything I can find seems geared towards multiple servers, rather than provisioning a VM and/or an AWS instance identically.
Anyone got some good resources for it?
Earlier quoted context omitted.
Cask could be awesome, but it's not at this stage. There are no upgrades, in many cases it doesn't work. Most apps complain that they are not in /Applications, but are in ~/Applications instead and so on. At the end of the day, it duplicates some of the Homebrew functionality - some non-GUI packages are getting into Cask, because possibly Homebrew doesn't want them - it's a bit confusing as well. I think efforts shou…
Hiya - author here. Thanks for the feedback on this stuff! It's always good to hear where it's best to focus improvements. I'm going to address a few of your points specifically. > There are no upgrades, in many cases it doesn't work. It's true that `brew cask upgrade` is not yet a thing. I would very much like it to be. I've been sort of avoiding work on the feature for fear of messing it up. But that's no reason to…
Earlier quoted context omitted.
Huh… I’ve installed 17 Casks; no apps have complained about being in ~/Applications. In fact, for properly written apps, it should not matter, so there may be something else going on. I’ve been using ~/Applications forever for beta testing and accessing two different versions of the same app.
That's true. I hope more apps improve as well as OS X itself. The issue with ~/Application seems to be OS X-related as reported by HyperSwitch ( http://bahoom.com/hyperswitch/ ), which cannot run in background without being under /Applications.
One blind spot that all of these OS X configuration tools appear to have is the App Store. Not through any fault of their own I suspect... more that Apple hasn't opened the App Store app to being scriptable. But a command-line way of installing/reinstalling/updating App Store apps would be great.