- Expediere
- 27 septembrie 2026 la 22:01 UTC
- Autor
- Kamo
- Comite
- 88b06ef
KamoFamily is a new Next.js site (Forgejo kamo/kamofamily, edited on GitHub pantherkamo/KamoFamily), set up the same way as the KamoUniverse marketing site: - auto-cert: dev.kamofamily.com in STATIC_DOMAINS - poddisruptionbudgets: kamofamily, maxUnavailable 1 (2 replicas) - git-sync: CronJob git-sync-kamofamily fast-forwards Forgejo main to GitHub main every two minutes (applied by hand, like the first one) auto-cert only ever seeded STATIC_DOMAINS once, at startup, and that seed skips a host whose DNS does not resolve. Nothing revisited it, so a domain listed before its record existed waited for the next pod restart. dev.kamouniverse.com hit this two days ago and got its cert only because a request happened to land in the access log. dev.kamofamily.com is listed while kamofamily.com is still delegated to Yahoo's retired nameservers, so it would hit the same gap. The main loop now re-runs the seed about every 15 minutes for static hosts without a healthy certificate. When every host has one, it logs nothing.