<feed xmlns='http://www.w3.org/2005/Atom'>
<title>skiff.git/internal/tmpl/tmpl.go, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.mikeanthonywild.com/skiff.git/atom?h=master</id>
<link rel='self' href='https://git.mikeanthonywild.com/skiff.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.mikeanthonywild.com/skiff.git/'/>
<updated>2026-09-03T02:00:08Z</updated>
<entry>
<title>Add domain and TLS management via skiff domains add/remove/list</title>
<updated>2026-09-03T02:00:08Z</updated>
<author>
<name>Claude</name>
<email>noreply@anthropic.com</email>
</author>
<published>2026-09-03T02:00:08Z</published>
<link rel='alternate' type='text/html' href='https://git.mikeanthonywild.com/skiff.git/commit/?id=6040eff2d2b4618f19d4615d246ea6b0704acdf8'/>
<id>urn:sha1:6040eff2d2b4618f19d4615d246ea6b0704acdf8</id>
<content type='text'>
Replaces the single server_name string in meta.json with a domain list
(one primary, others redirect to it) and TLSDomains tracking what the
app's certificate actually covers. Certs are issued/expanded via certbot
certonly (webroot, never the --nginx plugin, since Skiff owns and
regenerates skiff.d/*.conf itself) as one SAN cert per app, matching how
a real multi-domain vhost is normally issued.

Domain/TLS changes never touch the jail - no restart, no health check -
since they only affect nginx and the certificate. `add` is safe to retry
if DNS isn't ready yet; `remove` never calls certbot at all, so it can't
fail on an ACME/network problem.

Also updates README/USER_GUIDE for the new command surface, one-time TLS
host setup (certbot register, renewal cron, reload hook), the --ip
same-subnet requirement for jails to reach the network at build time, and
the actual base-image provisioning sequence (pkg needs an explicit
bootstrap after bsdinstall; versioned port names like go125 need a
default symlink) - all found and fixed live while getting this working
end-to-end on a real FreeBSD VM.

Co-Authored-By: Claude Sonnet 5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
<entry>
<title>new-app: configure jail mail relay and persist the jail's network alias</title>
<updated>2026-08-26T02:23:04Z</updated>
<author>
<name>Claude</name>
<email>noreply@anthropic.com</email>
</author>
<published>2026-08-26T02:23:04Z</published>
<link rel='alternate' type='text/html' href='https://git.mikeanthonywild.com/skiff.git/commit/?id=2a9ca0577ecdbee8b5a4bc8886c112dbc4260eab'/>
<id>urn:sha1:2a9ca0577ecdbee8b5a4bc8886c112dbc4260eab</id>
<content type='text'>
Two provisioning gaps in new-app:

- The jail's dma.conf inherited the base image's shared SMARTHOST/
  PORT/AUTHPATH, but never got a per-app MAILNAME - without one, dma
  can misroute mail for recipients on the jail's own apex domain as
  local delivery. EnableMail appends a MAILNAME of &lt;app&gt;.skiff.local,
  which can't collide with any real domain an app sends to or from.

- A classic jail's ip4.addr is only a bind restriction, not a route,
  until something aliases it onto a host interface. jail.conf.tmpl
  never set jail(8)'s own `interface` parameter, so nothing ever
  created that alias - confirmed on skiff-freebsd, where the address
  had twice been made to work via an ad hoc `ifconfig alias` that
  didn't survive a reboot. Setting `interface` lets jail(8) manage
  the alias itself, including on every boot.
</content>
</entry>
<entry>
<title>Initial commit of skiff scaffolding</title>
<updated>2026-08-06T04:14:29Z</updated>
<author>
<name>Claude</name>
<email>noreply@anthropic.com</email>
</author>
<published>2026-08-06T04:14:29Z</published>
<link rel='alternate' type='text/html' href='https://git.mikeanthonywild.com/skiff.git/commit/?id=9f7c9f2f31acd7bc544dd988af1c8c2fe63ec504'/>
<id>urn:sha1:9f7c9f2f31acd7bc544dd988af1c8c2fe63ec504</id>
<content type='text'>
</content>
</entry>
</feed>
