this post was submitted on 15 Aug 2023
41 points (97.7% liked)

Technology

59300 readers
5014 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

cross-posted from: https://programming.dev/post/1743099

.yaml, .toml, etc?

you are viewing a single comment's thread
view the rest of the comments
[–] exu@feditown.com 6 points 1 year ago (1 children)

For simple stuff, INI is pretty good.

I must admit I've written stuff that uses a JSON config file, but I might finish implementing YAML instead. Any day now...

[–] JoeClu@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (2 children)

Agreed about INI for simple stuff. Not good for arrays and nested things though. Usually use binary for that type of config (with clear documentation). Most binary config files I use are plain old C structures. I'm not a web person so no need to make the config plain text.

[–] the_third@feddit.de 1 points 1 year ago

This human would prefer YAML for that, especially if I had to generate/modify said config in Ansible/puppet/whatever.

[–] SubArcticTundra@lemmy.ml 1 points 1 year ago

You could use TOML. It's pretty much an extension of INI