-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kyma infra docker #6
base: main
Are you sure you want to change the base?
Kyma infra docker #6
Conversation
- Wildfly driver | ||
- keycloak | ||
|
||
How to deploy the apps |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was able to get through the process, but by linking out to instructions in other readme files, etc. it was hard to discern where I should stop following the instructions in those and come back to this.
As a for instance, it points to https://github.com/migtools/playpen/tree/main/ec2#readme where I guess I was to run these:
cp sample.my_vars.yml my_vars.yml
./create_infra.sh
But then I shouldn't run ./setup_nodes.sh
?
But it did appear necessary to download jboss-eap-7.4.0.zip
later in the instructions.
I think it would be easier to follow if this is just a bullet or numbered list with the exact steps required to run deploy the environment.
------------- | ||
|
||
* Infra setup: | ||
* Server: fedora 38 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should bump this to at least 39 if it doesn't cause problems. I didn't note any going through the process. F40 is well on the way and 38 will be EOL soon after. Better would probably be something with a longer life per release like RHEL/CentOS Stream, but understand if that presents difficulty we don't need to spend time on right now.
Setup:
Server: fedora 38
docker
EAP 7.4 using java 8
EAP running on port 8080
Quarkus using java 11
Quarkus running on port 8085
Java versions and quarkus installations are managed by sdkman
manual maven install
uses roles from migtools/playpen repo to create ec2 instance and configure eap
note: eap should use standalonefull config