Tag Archives: chef

A Taste of Salt: Like Puppet, Except It Doesn’t Suck

Perhaps the most compelling aspects to SaltStack is its vibrant community. Despite Puppet’s nearly six year head start, Salt boasts more contributors to its code base (as per Ohloh.net), a superior comment-to-code ratio, an increase in year-over-year commits, and a lower barrier to entry for new contributors. Community support is provided both via an active IRC channel (#salt on irc.freenode.net) and on the salt-users mailing list.

(Full Story: http://blog.smartbear.com/devops/a-taste-of-salt-like-puppet-except-it-doesnt-suck/ )


Introduction to Chef – FOSDEM 2013 // Speaker Deck

Quick introduction to Chef given at FOSDEM 2013. The code for this presentation can be found at https://github.com/nathenharvey/wordpress-quick-start

(Full Story: https://speakerdeck.com/nathenharvey/introduction-to-chef-fosdem-2013 )

Chef cookbooks for busy Ruby developers

Have you ever setup a Rails production environment from scratch, by hand? Two Chef cookbooks to automate the process: rackbox – to provision rack-based web server (Nginx as front server, Unicorn and Passenger as upstream app servers, rbenv as ruby version manager). databox – to provision database server (supports MySQL and PostgreSQL).

(Full Story: http://teohm.github.io/blog/2013/04/17/chef-cookbooks-for-busy-ruby-developers/ )

Give Vagrant a Place in Your Workflow

Provisioning services like this is a real swiss army knife for a developer. We get some ‘best practice’ from the curators of the cookbooks we use for the chef run and a nice workflow with Vagrant. It is worth pointing out, and I may only be speaking for myself, I use the provisions and chef runs to only get me so far. It’s dev-ops. I have enough knowledge to be dangerous when it comes to provision servers for personal applications. I have no need or desire to go any further tweaking my boxes. Anything production worthy I recommend getting some expert advice from a sys-admin.

(Full Story: http://rubysource.com/give-vagrant-a-place-in-your-workflow/ )

Automating the setup of my perfect developer environment on OSX

Using Chef to automate all these tasks for me has been a revalation for me, while i’m sure that there will be many many improvements in the next months, I’ve found that this system allows me te exactly recreate and configure my developer environment. But as always, some things are still missing. Triggering installs from the App Store, entering licences, configuring Mail.app etc. All things to research in the future. If I find anything of note, be sure to expect followups.

(Full Story: Automating the setup of my perfect developer environment on OSX)

Intro to Chef – Java Code Geeks

Chef is an incredible tool, but despite its beginnings in 2008/2009 it still lacks an effective quick start, or even an official “hello world” – so it takes too long to really get started as you desperately search for tutorials/examples/use cases. The existing quick starts or tutorials take too long and fail to explain the scope or what Chef is doing. This is really unfortunate because the world could be a better place if more people used Chef (or even Puppet) and we didn’t have to guess how to configure a server for various applications.

(Full Story: Intro to Chef – Java Code Geeks)

devopsanywhere: Puppet vs. Chef, Fight!

Chef wins but by only a narrow margin.

The Criteria

Community Strength
Corporate Adoption
Technical Merits
Hands-on Experience

(Full Story: devopsanywhere: Puppet vs. Chef, Fight!)

How Ruby is beating Python in the battle for the Soul of System Administration

Here are the features in a scripting language that a sysadmin wants:
A DSL for the problem domain
High productivity, i.e. concise and expressive syntax
Easy to interaction with shell commands
Regular Expressions
powerful one-liners

(Full Story: How Ruby is beating Python in the battle for the Soul of System Administration)