Skip to content
This repository was archived by the owner on Sep 2, 2021. It is now read-only.
This repository was archived by the owner on Sep 2, 2021. It is now read-only.

Config changes and updates #30

@Munsio

Description

@Munsio

One big problem i encountered is that every time we change something in our config files (bugfixes and so on) and you upgrade the stack, in the first step you need to change the name of the config folder or something like that or those files don't get overwritten.

But before we could provide an answer we need to define the behaviour we want, i have following ideas for that: (Note: these change is only for config files under /examples/rancher-gen )

  1. We don't care about changes by the user and overwrite these config files on each startup.

  2. We generate an hash from the existing file and check if it is the same hash then the version before - if thats true we overwrite it - if not we write it to the logs that some changes needs to be done. (Problem here might be that a wrong configuration don't let the container start)

One huge problem would be that if we include other config files in the current one thats not always possible (nginx.tmpl)

Input welcome

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions