Just to clarify, when I say develop locally, I mean _not_ using
k8s/OpenShift/Minishift/cluster up/etc at all, but just using a local
EAP/JWS/etc install.
On Mon, Oct 1, 2018 at 9:28 AM Andre Dietisheim <adietish(a)redhat.com> wrote:
Am 01.10.18 um 16:28 schrieb Rob Cernich:
it seems to assume that folks are doing their development using an
OpenShift/k8s instance. If it were me, I'd be doing my dev locally,
without any of this stuff, not hitting OpenShift/k8s until my work was
mostly polished (i.e. developing against a local server, maybe running it
in a local container, just to save the install hassle).
+1 on this, I'd go for the same while I hear in many "big corp/project"
presentations that they test in the cloud (AWS etc. bcs they rely on AWS
services).
I actually tried to cover this approach by asking whether running locally
is the approach that is used. Maybe this isn't obvious enough?
Maybe a follow up question would then be how they mock the env in this
case?
On Mon, Oct 1, 2018 at 6:56 AM Andre Dietisheim <adietish(a)redhat.com>
wrote:
> Hi
>
> I made a first draft for the survey we're about to send out to customers
> in Switzerland at:
>
>
https://www.surveymonkey.com/r/Preview/?sm=Emrpg319fDR_2BId4ONQlvKDliKriz...
>
> The goal is to find out how developers code with/against
> Kubernetes/OpenShift and to accordingly find out what we should offer
> them in our tooling.
>
> Please feel free to comment and suggest anything that could be
> improved/corrected.
> Thanks for the feedback!
>
> Cheers
> André
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev