Comment by zamadatix

4 hours ago

Never thought I'd see hackers saying INI format looked ugly of all things. It's basic, sure, but that's a good thing for something meant to be easily editable by hand from any editor. Otherwise, it's just key value pairs in named sections, how ugly can it be about that?

9 comments

zamadatix

jjgreen 3 hours ago

key-value pairs where the = cannot be surrounded by spaces, so I have to write

  [Service]
  Type=oneshot
  WorkingDirectory={{ home }}/current/
  Environment=RAILS_ENV=production
  ExecStart=/bin/sh -lc "bin/db-backup --verbose"

which fills me with sadness

voxic11 3 hours ago

Whitespace immediately before or after the equals sign is completely ignored by the parser. Its the standard INI format.

yjftsjthsd-h 3 hours ago

What? You absolutely can have spaces; most of mine look more like

  [Service]
  Type             = oneshot
  WorkingDirectory = %h/current/
  Environment      = RAILS_ENV=production
  ExecStart        = /bin/sh -lc "bin/db-backup --verbose"

jjgreen 3 hours ago

Friend, you have changed my life

2 replies →

ramon156 3 hours ago

TOML would look a lot more quiet, but I'm not sure if TOML would be a good fit

kevinmgranger 3 hours ago

unit files barely have any nesting, so the INI-like format is already 90% of the way towards TOML, no?