supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Joshua Timberman <joshua@opscode.com>
To: Peter Hickman <peterhickman386@googlemail.com>
Cc: "<supervision@list.skarnet.org>" <supervision@list.skarnet.org>
Subject: Re: Installing on Centos
Date: Thu, 9 May 2013 09:37:53 -0600	[thread overview]
Message-ID: <020941F9A16E4D1F942255D10D9B9738@opscode.com> (raw)
In-Reply-To: <CALxYQy4Kzb7LOza80icg1CBBeHan_DXPGne1JzPuqfT_3stB5g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 692 bytes --]

On Thursday, May 9, 2013 at 7:03, Peter Hickman wrote:
> All our chef scripts were written with ubuntu 10.04 in mind and we had not
> correctly separated the os dependencies from the application deployment.
> Then we had to deploy to Centos :)
> 
> 

Opscode's runit cookbook supports CentOS (and other EL family distros) first class now, in version 1.0 and higher of the cookbook. It is a complete installation solution via the default recipe, and the runit_service resource is a fully developed feature complete service resource. 

http://ckbk.it/runit

I'm biased of course since I wrote the code, but I think this is the best way to manage runit if you're using chef already. 

-Joshua 


      parent reply	other threads:[~2013-05-09 15:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07  9:30 Peter Hickman
2013-05-07 10:56 ` Alex Efros
2013-05-07 11:17   ` Peter Hickman
2013-05-07 17:47     ` Joshua Timberman
2013-05-09 13:03       ` Peter Hickman
2013-05-09 14:49         ` Charlie Brady
2013-05-09 15:05           ` Peter Hickman
2013-05-09 15:08             ` Charlie Brady
2013-05-09 15:37         ` Joshua Timberman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=020941F9A16E4D1F942255D10D9B9738@opscode.com \
    --to=joshua@opscode.com \
    --cc=peterhickman386@googlemail.com \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).