Skip Navigation
grumpydeveloper grumpydeveloper @programming.dev
Posts 1
Comments 2
Plugins and config file

  • ok, thank you all for your replies.

    Both sides have good arguments, that's why I was posting this, many of the argument came up as well when arguing with myself.

    Counting the posts/upvotes, split config files seem to be the most popular choice or is it just because of they were the oldest and had time to collect more upvotes? Questions after questions :)

    Thanks and cheers

    Grumpy

    •
    Plugins and config file

  • As it is a more theoretical question or a question for the next time I need this, making config file(s) read-only and giving guidelines on how to structure the config values is possible. good points. Applies to all possible solutions 1-4 ;)

    • Programming @programming.dev grumpydeveloper @programming.dev

    Plugins and config file

    Hi,

    I'm asking for opinions and preferences.

    There is no right or wrong.

    Scenario:

    I have a tool (server component, api only, no gui) that has a config file and no per-user adjustable things. The admin can change things, of course.

    Now the tool gets plugins, where to configure them?

    1. All in one config file with plugins having a section for their things,
    2. plugins get their own config file.
    3. the main config points to a storage (database) with config options for everything, a kind of variant of 1.
    4. something else/better

    Hoping for a civil discussion ;)

    Cheers

    Grumpy

    9