Skip to content

Generate default config file during build #67

@theborakompanioni

Description

@theborakompanioni

Shipping a default config file is cumbersome and effectively unnecessary.
You have to track JM releases closely and make sure to ship the "right" default values.
With #66 merged, there is no real need anymore to ship this file.
JM will create a standard config file on first start, which can be done during the docker build process.
The current behaviour of env var RESTORE_DEFAULT_CONFIG can stay the same, if this file is copied to different directory immediately afterwards.

Users will still be able to include their own config file. Also, all env variables prefixed with JM_ will overwrite corresponding config variables.

Info: The mechanism of applying env vars to the JM config must be able to handle commented out variables.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions