(Note: this is one of several guides possible related to integration with an external datasource. Be sure to familiarize yourself with the overall set to be sure what you do will fit nicely with the others.)
NOTE: I say MariaDB here, but if a different DB supported by wildfly-datasources-galleon-pack is a better choice, we can use that. It needs to be one that doesn't require purchasing/licensing etc as the guide should cover installing the DB. PostgreSQL is handled by a different issue.
This would use an example app that uses a datasource. Perhaps kitchensink QS.
Use of wildfly-datasources-galleon-pack as part of provisioning a WildFly installation.
Installation of MariaDB using docker.
Setting env vars to control datasource configuration.
Launch and run.
Follow-on guides:
Integrating with a PostgreSQL database on k8s/OpenShift (This will use PostgreSQL, but the content difference between this guide and the base 'Integrating with a PostgreSQL database' is easy enough to apply to a MariaDB context.)
(Note: this is one of several guides possible related to integration with an external datasource. Be sure to familiarize yourself with the overall set to be sure what you do will fit nicely with the others.)
NOTE: I say MariaDB here, but if a different DB supported by wildfly-datasources-galleon-pack is a better choice, we can use that. It needs to be one that doesn't require purchasing/licensing etc as the guide should cover installing the DB. PostgreSQL is handled by a different issue.
This would use an example app that uses a datasource. Perhaps kitchensink QS.
Use of wildfly-datasources-galleon-pack as part of provisioning a WildFly installation. Installation of MariaDB using docker. Setting env vars to control datasource configuration. Launch and run.
Follow-on guides:
Integrating with a PostgreSQL database on k8s/OpenShift (This will use PostgreSQL, but the content difference between this guide and the base 'Integrating with a PostgreSQL database' is easy enough to apply to a MariaDB context.)
Related guides:
Integrating with a PostgreSQL database #577