* Overwrite config settings with comments correctly
Comments were either removed or broke the setting value due to incorrect formatting
* Fix "webUIEnabled" env var name
* Delete container only after receiving its logs
Due to the "-rm" option when starting the container, it was immediately deleted after it was stopped.
This prevented the workflow from getting the containers logs since it didn't exist anymore at this point of time and instead an error was raised
* Print container logs in case of failure
* Add a workflow step to test the container with passing env vars
* Overwrite server.conf settings only for provided env vars
Currently on every start the whole server.conf file gets replaced which causes any changed settings during runtime to get lost
* Fix readme formatting
* Add "webUIEnabled" env variable
This is the only setting that can not be changed via the UI
* Remove default values from readme
If we explicitly set the user.home property, then Java doesn't consult
/etc/passwd to determine $HOME, fixing the problems that necessitated
updating /etc/passwd in the first place.
Signed-off-by: Chance Zibolski <chance.zibolski@gmail.com>
Because we use the Java user.home property to get the default
configuration directory, there needs to be an entry for the correct user
in /etc/passwd. For this to work with arbitrary UID/GID, that means
updating /etc/shadow dynamically based on the UID/GID in the container
before starting the application.
Signed-off-by: Chance Zibolski <chance.zibolski@gmail.com>
