As there is very little chatter here about a CentOS version of Quickstart, maybe I'm missing something. As a lightweight Linux sysadmin at best and my live sites hosted on CentOS, I know just enough CentOS to manage those servers.

Having a CentOS Quickstart version allows me to get by without knowing a thing about Ubuntu. I'm sure there are a few others riding in my boat but very few request for another port. Maybe there is not enough difference to sweat or what am I missing?

Comments

TravisCarden’s picture

The best bet for supporting alternative OS flavors is probably to move away from focusing on disc images to using Vagrant or the like.

bhosmer’s picture

I've thought of this myself and what might be the best way to abstract things, and I came to the conclusion that quickstart might not be the best tool for multi-distibution development environments. Personally, I use #1, a combination of vagrant and a configuration management tool for CentOS/Ubuntu testing.

MichaelCole’s picture

Hey Don and Ben,

There is a Puppet script repo on GitHub that already works for CentOS. https://github.com/quickstart/quickstart-configure

We'd like to extend it to Ubuntu, and then use it as a basis for the server version. My understanding is that would mean the same server for both CentOS and Ubuntu.

We're looking for someone who understands Puppet to help. Would either of you be interested?

Mike

bhosmer’s picture

I have a general understanding of puppet, but not much in-depth. My configuration management of choice is SALT instead, but I'll take a peek at it and see.

Just for an example, here is a Drupal SALT State that I created: https://github.com/saltstack/salt-states/blob/master/small/lamp-drupal/i...

Personally, I find it much easier to read and extend than puppet manifests. It also can very easily be extended to encompass RHEL/CentOS support as well. I use this state currently with vagrant already.

An example of extending it would be:

{% if grains['os'] == 'CentOS' %}

Do something!

{% endif %}