- From: Bryan Berry <
>
- To:
- Subject: [chef] Re: Re: Re: Re: lwrp based on the omnibus configuration DSL ?
- Date: Wed, 31 Jul 2013 15:14:21 +0200
hey Brian, I sometimes do compile stuff in chef runs, often for developer
setups
as for production scenarios, i rarely use ./configure && make && make
install but i do often
do several arbitrary steps after unpacking a tarball, esp. for dynamic
languages like python or ones w/ bytecode interpreters like java
I don't actually use nginx, i just used it for an example. Most of my
current apps are either ruby, java, or python
On Wed, Jul 31, 2013 at 3:06 PM, Brian Akins
<
>
wrote:
>
Not what you were asking about, but why don't you use omnibus to build these
>
packages then just install them via chef-client (remote_file + gdebi/yum)?
>
Maybe with some tooling around omnibus-ruby and vagrant and you could have a
>
CI pipeline for them as well.
>
>
It feels "odd" to be compiling a bunch of stuff at deployment time. Yes, I
>
admit to doing it, but I've never been happy doing it.
>
>
Shamelss plug: https://github.com/bakins/omnibus-nginx - patches welcome. A
>
"directory" of omnibus projects would be helpful to avoid duplicated effort,
>
or at least to be used as examples.
Archive powered by MHonArc 2.6.16.