Domain model, used by repositories, converters and impl.
Static resources as images (logo, favicon, track/stream images) and templates needed for different conferences. Used by converters, was used by impl.
Contains logic to convert conference input to internal data structure to be served to client applications.
Server implementation with dynamic features as favorites, preferences and keycloak configuration.
Formerly it also contained dynamically served conference data which was now moved to converters where it will be generated as files which will be served as static content from edge service.
This feature is enabled by default but can be deactivated as Spring Boot configuration value conferences.read
, e.g., at startup with --conferences.read=false
.
Parameterizable standalone java application for reading conference input and saving json files and images to serve from edge server statically. This content was generated dynamically in impl lately and was moved to converters.
Accessible on /rest/conferences/499959
.
Data is being cached.
Data can be updated with URI /rest/conferences/update/499959
.
Therefor an authenticated request with role ROLE_ADMIN
is needed.
- Login with Keycloak
- Filters will be persisted with a record of each principal in the DB
- Write/save:
- HTTP method
PUT
- URL
http://localhost:8080/rest/filters
- Content-Type:
application/json
- Payload:
{"favourites":true,"levels":["Fortgeschritten"],"languages":["Englisch"],"tracks":["IDEs & Tools"],"locations":["Wintergarten", "Schauspielhaus"]}
- HTTP method
- Read:
- HTTP method
GET
- URL
http://localhost:8080/rest/filters
- HTTP method
Health check is available at /health
URI.
HTTP status code 200
of the response tells you that everything is ok.
- H2 in development mode
- In-Memory (
jdbc:h2:mem:testdb
) - DB console:
http://localhost:8080/develop/h2-console/
- In-Memory (
- PostgreSQL with profile "postgresql"
- activate with
-Dspring.profiles.active=postgresql
- to run the tests against the PostgreSQL db (and a previously reset of the db), you need the "postgresql-test" profile (
-Dspring.profiles.active=postgresql-test
)
- activate with
- Maven build fails in verify phase if declared dependencies are unused or used dependencies are undeclared
- mvn verify
- CI calls mvn deploy which includes verify
- the acutal goal is mvn dependency:analyze(-only) which may show warnings
- dependency analyzing may cause problems because of Spring Boot starter dependencies
- configure in pom.xml
Start org.dukecon.DukeConServerApplication from your IDE.