Collection of cookbooks for Podman Quadlets

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: ee66d557de

feat/base-partitioning-to-local

feat/home-assistant-cookbook

feat/lego-v5

feat/netbird-cookbook

feat/zwave-js-ui-cookbook

fix/network-host-resolv-conf

main

v0.0.1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'ee66d557de'

${ noResults }

podman-quadlet-cookbook/cookbooks/lego/config

History

Nicolas Massé 75513c11c2 lego: migrate to lego v5 and its YAML configuration file - A single oneshot lego.service (lego --config /etc/lego/lego.yaml) obtains and renews the certificates, triggered at boot and daily by lego.timer. - The deploy hook flags the certificate as renewed; lego-hooks.path then runs renew-hooks.d/*.sh on the host, on the first issuance and on each renewal. - lego.target only Wants lego.service: an ACME failure does not stop the target and the timer retries. - Consumers rely on the fixed certificate ID "default". - Dev mode generates a self-signed "default" certificate. - Document the v4 to v5 upgrade (reissue) and add pytest integration tests against Pebble. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NMEYncwy1yEBJCSb8HLgXg		2 weeks ago
..
examples	lego: migrate to lego v5 and its YAML configuration file	2 weeks ago
deploy-hook.sh	lego: migrate to lego v5 and its YAML configuration file	2 weeks ago
process-hooks.sh	add hooks for lego certificate renewal + self-signed certificate generation when in dev mode	5 months ago