Further details
Database🔗
Liquibase is used to manage Chutney RDBMS schema.
You can find corresponding changelog here.
Note
- Chutney is tested with SQLite, H2 and PostgreSQL databases.
- Chutney configure those database throught spring profiles.
db-h2for H2,db-sqliteordb-sqlite-rw(different datasources for read and write) for SQLite anddb-pgfor PostgreSQL - You can find complete examples in maven module chutney/server, for all three database types.
To configure your datasource, use the property spring.datasource
Logs🔗
Chutney uses SLF4J with Logback as the runtime implementation.
A default logback.xml is packaged in the server jar and logs to the console at level WARN.
Warning
Do not add logging bridges yourself — they are already included.
Avoid:
jcl-over-slf4jlog4j-over-slf4j/slf4j-reload4jjul-to-slf4j
For complete details, see the Spring boot logging documentation.
Below are just a few common examples.
Override the log configuration🔗
You can replace or adjust the default logging without repackaging.
Use a custom Logback file🔗
Quick tweaks via application.yml🔗
For simple level changes:
Use a full Logback file if you need to change appenders or patterns.
Server (TLS/SSL)🔗
Chutney server enforces the use of secure calls on any incoming requests.
Server HTTPS configuration
Chutney Server provides undertow-https-redirect Spring profile to redirect unsecured request to the right secured port.