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

Re: Using a custom git template without customizing the cart




----- Original Message -----
> 
> 
> ----- Original Message -----
> > From: "Clayton Coleman" <ccoleman redhat com>
> > To: "Luke Meyer" <lmeyer redhat com>
> > Cc: "Openshift Dev" <dev lists openshift redhat com>
> > Sent: Tuesday, January 21, 2014 12:14:34 PM
> > Subject: Re: Using a custom git template without customizing the cart
> > 
> > 
> > 
> > > On Jan 21, 2014, at 12:02 PM, Luke Meyer <lmeyer redhat com> wrote:
> > > 
> > > Putting anything in the manifest is still a custom cart... have to
> > > fork it and maintain that.
> > > 
> > > I think some conf at the broker that supplies a default --from-code
> > > URL would suffice. That way the template could either be centrally
> > > managed in an external repo, or installed on all the nodes
> > > (possibly with variations) at file:///...
> > 
> > We disallow file:// urls for security reasons.  I think we might want
> > to keep that restriction for various reasons.  Organizations using
> > git can host those elsewhere if necessary, or in an app.
> 
> True. But file:// would give the ability to customize per node, which might
> be handy. Probably not immediately necessary, but... what if
> file:///etc/openshift/cart.conf.d/templates/* were allowed? In fact, the
> node could just use entries in there by default if they existed...
> 

Just seems better to centralize the templates and require an organization to put them somewhere.  An app on openshift, an apache server, Github, etc.


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