BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.all-systems-go.io//PXBVLE
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-all-systems-go-2026-PXBVLE@cfp.all-systems-go.io
DTSTART;TZID=CET:20260930T150500
DTEND;TZID=CET:20260930T153000
DESCRIPTION:For a while\, the standard way to run Podman containers under s
 ystemd was podman generate systemd. It worked\, but the output was static 
 and awkward to maintain. Quadlet replaced it — and most guides stop at "
 drop an INI file in a directory and your container starts." leaving the ma
 chinery a black box. \n\nThis talk demystifies that black box\, because th
 e internals are exactly what you reach for when things break. Quadlet isn'
 t a daemon. It's a systemd generator that runs at daemon-reload and turns 
 your .container\, .pod\, and .network files into ordinary .service units. 
 \n\nIn session\, we'll trace one stack example from end to end\, watching 
 a three-line container file expand into a full podman run command\, and cr
 oss-unit references become injected After=/Wants= dependency edges with na
 me-mangled volumes and networks.\n\nYou'll leave knowing exactly what gets
  generated\, why edits need a daemon-reload\, how to dump & debug a failin
 g unit yourself\, and explain why keeping only the source files under vers
 ion control is reliable. Less magic\, more model.
DTSTAMP:20260815T235756Z
LOCATION:Galerie
SUMMARY:Forget "podman generate systemd": How Quadlet Really Works - Kritik
  Sachdeva
URL:https://cfp.all-systems-go.io/all-systems-go-2026/talk/PXBVLE/
END:VEVENT
END:VCALENDAR