Wildfly mini serie #595
Wildfly mini serie #595
Conversation
|
|
||
| include::{includedir}/_prerequisites.adoc[] | ||
|
|
||
| * link:/get-started[Getting Started with WildFly] |
There was a problem hiding this comment.
I think it should be official step in the guide.
|
|
||
| == Maven Project | ||
|
|
||
| In link:/get-started[Getting Started with WildFly], we created a simple Jakarta EE application Maven Project containing a link:https://jakarta.ee/specifications/restful-ws/[Jakarta RESTful Web Service]: we'll pick up from there; |
There was a problem hiding this comment.
Yep, here. Just changing the wording to something like go through "Getting Started with WildFly"....
| </goals> | ||
| </execution> | ||
| </executions> | ||
| </plugin> |
There was a problem hiding this comment.
Is it possible to use Wildfly Glow here? I find it much more user friedly.
There was a problem hiding this comment.
I prefer not to use glow, since its usability was under discussion... it might be yet another post in this mini-serie
| include::{includedir}/_prerequisites.adoc[] | ||
|
|
||
| * link:/get-started[Getting Started with WildFly] | ||
|
|
There was a problem hiding this comment.
I'm missing "docker/podman" mentioned in prerequisites.
|
|
||
| NOTE: we explicitly mapped port `8080` in the container to port `8080` on the HOST (your PC); we also mapped port `9990` in the container to port `9990` on the HOST to expose the Liveness, Readiness and Startup Probes; | ||
|
|
||
| === Check the application |
There was a problem hiding this comment.
I'm not sure about duplicating the steps to check the when they're the same as above. Maybe it could be mentioned that it can be checked the same way as above (+link)
|
|
||
| === pom.xml | ||
|
|
||
| Since we are going to deploy on link:https://kubernetes.io/[Kubernetes], we need to add some features that are necessary when running on link:https://kubernetes.io/[Kubernetes]: link:https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/[Liveness, Readiness and Startup Probes]; |
There was a problem hiding this comment.
I think it could be mentioned here that Kubernetes will be needed in the 2.part of the gude and it's not necessary to install it at this point.
| In this guide, you will learn how-to run the Docker Image we built in link:simple-microservice-part1[{simple-microservice-part1}] on Kubernetes. | ||
|
|
||
| include::{includedir}/_prerequisites.adoc[] | ||
| * You have completed link:simple-microservice-part1.adoc[Create a JAX-RS application using Bootable Jar - part one: bare metal] |
There was a problem hiding this comment.
It would deserve to add step with link to guide how to install Kubernetes intance locally which would be used in next steps. I think it's quite a big thing so it might be another step in the guide.
|
|
||
| === Quay.io | ||
|
|
||
| You can skip this step in case you prefer to re-use the `quay.io/{quay-io-account-name}/{docker-image-name}` Docker Image, that we already pushed to link:quay.io[quay.io] in the `{quay-io-account-name}` account; |
There was a problem hiding this comment.
I think we should not mention here personal accounts. Better will be to use something general.
tommaso-borgato
force-pushed
the
wildfly-mini-serie
branch
from
63d0438
to
7057384
Compare
tommaso-borgato
force-pushed
the
wildfly-mini-serie
branch
from
442fb9a
to
1575d7e
Compare
tommaso-borgato
force-pushed
the
wildfly-mini-serie
branch
from
1575d7e
to
d57a544
Compare
#596
This mini-serie just aims at filling the gap we have at the very beginning of our learning path with WF+Microservices+Containers;
We aim at improving documentation for Wildfly/EAP and creating a series of blog-posts for users/customers. i.e. produce a step by step mini-serie which can be used to create a POC with Wildfly/EAP microservices running on Kubernetes; this would help new adopters who want quickly do a POC with the features they want (we start with basic features and, perhaps, add more later)