Programming

17374 readers

151 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Plugins and config file (programming.dev)

submitted 3 months ago by grumpydeveloper@programming.dev to c/programming@programming.dev

9 comments fedilink hide all child comments

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?

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

Hoping for a civil discussion ;)

Cheers

Grumpy

you are viewing a single comment's thread
view the rest of the comments

[–] grumpydeveloper@programming.dev 2 points 3 months ago

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