org.wcdevs.blog.core

Holds org.wcdevs.blog:core, the core application (API) where all the back-end RESTful services live in.

Contributing

Before start contributing to this project be sure you're familiar with our Contribution guidelines and our Code of Conduct.

Project structure

Root (parent) module: org.wcdevs.blog:core
Submodules:
- org.wcdevs.blog:persistence: contains all resources holding the logic to communicate with the persistence layer.
- org.wcdevs.blog:common: contains the common resources across the core application.
- org.wcdevs.blog:rest: contains the exposed webservices.

Local setup

Requirements

Development (do active Java code development)

Git
Java 17 (we use SDKMAN for Java versions management)
Maven (alternatively you can use the Maven wrapper by replacing all usages of the command mvn by ./mvnw)
Docker (and Docker Compose)
An IDE (such as Intellij IDEA or Eclipse)

Only running the API (run the whole stack to consume the API locally and view the API docs)

Git
Docker (and Docker Compose)

Running the application

Development mode

Clone the repo: git clone https://github.com/lealceldeiro/org.wcdevs.blog.core.git
Run docker-compose up -d wcdevs_db keycloak.service to start the database and the keycloak server

Note: macOS users must do instead docker-compose -f docker-compose.yml -f docker-compose-override-mac.yml up -d wcdevs_db keycloak.service
Run the Spring Boot application using your favorite IDE (use the local profile)

Running the API (whole stack) with docker compose

Clone the repo: git clone https://github.com/lealceldeiro/org.wcdevs.blog.core.git
Run

docker-compose -f docker-compose.yml -f docker-compose-override-keycloak-as-host.yml up -d wcdevs_db keycloak.service wcdevs_app

Note: macOS users must do instead

docker-compose -f docker-compose.yml -f docker-compose-override-keycloak-as-host.yml -f docker-compose-override-mac.yml up -d wcdevs_db keycloak.service wcdevs_app

It can be stopped then using docker-compose down.

For more info about docker compose run docker-compose --help.

Important: If you want to do log-in using the started keycloak server you need to update the hosts file of the operating system by adding the following entry. This is needed for the browser to be able to resolve this URL to the localhost started server by docker-compose.

127.0.0.1       keycloak.service

For more info about how to update the hosts file, please, check this StackOverflow post

Health check

To check the application is running you can hit this endpoint, which should return {"status": "UP"}: <base_url>/manage/health

Example request:

GET /manage/health HTTP/1.1
Host: localhost:82

Example response:

{
  "status": "UP"
}

API Docs

The API documentation can be seen once the app is up and running by navigating to <base_url>/docs/index.html. Example:

http://localhost/docs/index.html

Keycloak

To access the keycloak admin console navigate to http://localhost:8888 and login using as a username and password keycloak.

For more info see the keycloak docs

lealceldeiro/org.wcdevs.blog.core