[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: Using a custom git template without customizing the cart



----------------------------------------
> Date: Tue, 21 Jan 2014 14:25:01 -0500
> From: ccoleman redhat com
> To: lmeyer redhat com
> Subject: Re: Using a custom git template without customizing the cart
> CC: dev lists openshift redhat com
>
> Putting a git repo in an RPM is interesting... but they can also put that on an arbitrary system.
>
> ----- Original Message -----
>>
>>
>> ----- Original Message -----
>>> From: "Clayton Coleman" <ccoleman redhat com>
>>
>>>>> Just seems better to centralize the templates and require an
>>>>> organization to put them somewhere. An app on openshift, an apache
>>>>> server, Github, etc.
>>>>
>>>> Well, not that I disagree, but people have been known to want to do
>>>> things
>>>> differently.
>>>>
>>>> I'll start with the simple, centralized way though.
>>>>
>>>
>>> The best argument I can make for the simple way only is that if they
>>> expect that repo to change at all, then they need a process for
>>> updating every repo on every node. If they miss a node, they get
>>> some random inconsistent behavior that maybe no one notices. I
>>> don't know if organizationally I'd want to manage that (run pssh on
>>> all nodes and a git reset --hard origin/master etc)
>>
>> I have heard of these new-fangled systems for distributing identical content
>> across hosts, what were they called again? RPM and yum?
>>
>

One could use Satellite to maintain config channels (on templates that need to stay the same) and leverage the cheetah backend (for variable and snippet globalization) across the files that do require dynamic changes.


> _______________________________________________
> dev mailing list
> dev lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev 		 	   		  


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]