deleted
replykey-value pairs where the = cannot be surrounded by spaces, so I have to write
reply [Service]
Type=oneshot
WorkingDirectory={{ home }}/current/
Environment=RAILS_ENV=production
ExecStart=/bin/sh -lc "bin/db-backup --verbose"
Whitespace immediately before or after the equals sign is completely ignored by the parser. Its the standard INI format.
replyWhat? You absolutely can have spaces; most of mine look more like
reply [Service]
Type = oneshot
WorkingDirectory = %h/current/
Environment = RAILS_ENV=production
ExecStart = /bin/sh -lc "bin/db-backup --verbose"Friend, you have changed my life
replyIs this one of those cases where at one point you had an error in the file and you figured it was down to spaces? You fixed that issue, it still didn't work but from that point you never thought to question the assumption.
replyI find myself doing this sort of thing all the time..
Somewhere in my head I had that spaces caused a syntax error, and the UI for systemd is not obvious when you first start using it ... so if it's working then leave well alone. I'll be making all of my .service files (not so many) human-readable in the near future!
replyThat was (cough still is) ddclient for me.
replyMy epiphany a month ago was that I can use
reply Environment = MULTIPLE=environment VARIABLES="in single line"TOML would look a lot more quiet, but I'm not sure if TOML would be a good fit
replyunit files barely have any nesting, so the INI-like format is already 90% of the way towards TOML, no?
reply