Ready-to-code templates to start a project directly out of the box.
- basic-template: template dependency-injection-ready. Able to set config at appsettings.json. For basic & quick features testing
- crud-memory-ddbb: Rest API ready with Swagger and EF Core. It has an in-memory database for testing purposes
They compile as a fat jar through maven.
Kotlin is first compiled to java code, and this to binaries. This way it's possible to write Java classes at Kotlin projects for ease of use.
mvn clean install
java -jar [name].jar
They compile the same but the -cluster
option is needed for Hazelcast
and Vertx
to search for another microservices on launch.
mvn clean install
java -jar [name]-fat.jar -cluster
Everything that comes built through docker, comes with a Dockerfile and a docker-compose script so just docker-compose up
at the script level to start the service.
It uses a multi-stage image which builds upon a maven image and then deploys the resultant .jar into a Java image.
The build.sh script builds the image from docker-compose.yml and DockerFile, but does not start the container. This is useful to deploy into DockerHub when all changes are ready.
development.sh script builds the image from cache and starts a container with --watch option. This is useful to write posts, as it will automatically reload all changes on .md files.
Official images, without ini script. Initializes a blank database.
I'll try to put start scripts at the root folder for the rest of them.
For technical tests use the template: java-springboot-jpa-h2-rest
docker-jekyll --reload
option doesn't workkotlin-spring
doesn't compile. Allkotlin-springboot
variants do though