On Wed, Apr 6, 2016 at 6:34 AM, Hardy Ferentschik <[email protected]> wrote:
> Hi, > > Sorry to come back to this so late, but I tested the latest CDK build and > noticed several changes to the available templates, so I wanted to bring > this up > again. > > On Wed, 10-Feb-2016 13:33, Pete Muir wrote: > > 1) eap64-mysql-persistent-s2i > > Did you mean to only include the EAP + MYSQL template. Right now, > the plain EAP template (no database) is gone which seems wrong to me. Is > it? > I just saw eap64-basic-s2i in the installation I just ran > > Also is it really eap64-mysql-persistent-s2i (which is available now) or > should it be > eap64-mysql-ephermeral-s2i. The reason I am asking is, that the persistent > template makes > a persistent volume claim and we have not even setup any (there is an > outstanding pull > request to do so). I have not tried to use this template yet, but I am > wondering whether > it works. AFAIK no one has tested it. > > > 2) jws30-tomcat7-mysql-persistent-s2i > > 3) nodejs-mongodb-example > > 4) cakephp-mysql-example > > Another thing is that we still have builders for Python, Ruby and Perl > showing up. Maybe > not such a bad thing, but it was not in the list we initially defined. The > reason for this is > that we import the RHEL 7 image stream un-modified. I think we really need > to take control > over this and hand-roll our own streams and templates. > > That said, I am not sure whether there is still time to do much about the > imported resources. > Maybe we just need to fly with what we have, even though imo it is a bit > confusing to the users. > > At least the EAP issue should be investigated though. > > --Hardy > >
_______________________________________________ Container-tools mailing list [email protected] https://www.redhat.com/mailman/listinfo/container-tools
