https://github.com/teedjay/quarkus-database
Full dev service and continuous testing using postgres and mybatis
https://github.com/teedjay/quarkus-database
Last synced: 11 months ago
JSON representation
Full dev service and continuous testing using postgres and mybatis
- Host: GitHub
- URL: https://github.com/teedjay/quarkus-database
- Owner: teedjay
- Created: 2022-08-30T16:02:47.000Z (almost 4 years ago)
- Default Branch: main
- Last Pushed: 2022-08-31T11:57:53.000Z (almost 4 years ago)
- Last Synced: 2025-03-03T04:41:48.675Z (over 1 year ago)
- Language: Java
- Size: 15.6 KB
- Stars: 0
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# quarkus-database
This project uses Quarkus and requires Docker (dev services and continuous testing uses TestContainers).
The application demonstrates a minimum application that has the following features :
- [x] REST API using RESTEasy Reactive
- [x] Using MyBatis extension to query database
- [x] Using Records as simple `dto-type` (serialized to json by jackson and fetched from database using MyBatis)
- [x] Lokal dev and test database (PostgreSQL running on Docker)
- [x] Test REST API using full live stack of Quarkus + PostgreSQL
- [x] Automatically provision a local PostgreSQL development database (dev mode + dev services)
- [x] Tests will get own database provision a local PostgreSQL development database (dev mode + dev services)
If you want to learn more about Quarkus, please visit its website: https://quarkus.io/ .
## Running the application in dev mode
You can run your application in dev mode that enables live coding using:
```shell script
./mvnw compile quarkus:dev
```
> **_NOTE:_** Quarkus now ships with a Dev UI, which is available in dev mode only at http://localhost:8080/q/dev/.
## Packaging and running the application
The application can be packaged using:
```shell script
./mvnw package
```
It produces the `quarkus-run.jar` file in the `target/quarkus-app/` directory.
Be aware that it’s not an _über-jar_ as the dependencies are copied into the `target/quarkus-app/lib/` directory.
The application is now runnable using `java -jar target/quarkus-app/quarkus-run.jar`.
If you want to build an _über-jar_, execute the following command:
```shell script
./mvnw package -Dquarkus.package.type=uber-jar
```
The application, packaged as an _über-jar_, is now runnable using `java -jar target/*-runner.jar`.
## Creating a native executable
You can create a native executable using:
```shell script
./mvnw package -Pnative
```
Or, if you don't have GraalVM installed, you can run the native executable build in a container using:
```shell script
./mvnw package -Pnative -Dquarkus.native.container-build=true
```
You can then execute your native executable with: `./target/quarkus-database-1.0.0-SNAPSHOT-runner`
If you want to learn more about building native executables, please consult https://quarkus.io/guides/maven-tooling.
## Related Guides
- MyBatis SQL Mapper ([guide](https://quarkiverse.github.io/quarkiverse-docs/quarkus-mybatis/dev/index.html)): MyBatis SQL mapper framework for Java