...
...
| Note | ||
|---|---|---|
| ||
Hermod 3.x is based on Spring Boot 2.x, which means that many configuration properties have been renamed or changed. The deployment and configuration are NOT backward compatible with previous versions. The functionality and API of Hermod have however not been changed and are fully backward compatible. Manual update of the Hermod configuration file IS REQUIRED. Even though many updates are handled inside Hermod 3.x, you might need to change various parts of your configuration, depending on your setup. For general information, see https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.0-Migration-Guide. |
Prerequisites
| Expand | ||
|---|---|---|
| ||
The following prerequisites apply:
|
Step-by-step instruction
- Open the Hermod configuration file for editing.
Default file path: example/compose/hermod/config/cod-hermod.yml. - Update any needed settings according to the following guide: https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.0-Migration-Guide.
For example:Update servlet specific settings, for example the context path:
Change from...:Code Block title Example: Change from... server: contextPath: /...to:
Code Block title Example: Change to... server: servlet: context-path: /If you have configured some settings as start-arguments in docker-compose.yml, make sure to update these, if required.
- If any new spring properties are added, define them in kebab-case.
Spring 2.x has changed to kebab-case format for all properties. It is however stated that any camelCase properties are backward compatible, but any new properties you configure should be kebab-case to adapt for the future.
- Save the configuration file and restart Hermod.
- Test your new configuration on a non-production server, to make sure it works as expected.
Contact Nexus
If you need help or have any questions regarding your configuration files, feel free to contact Nexus.
...
Related information
...