<feed xmlns='http://www.w3.org/2005/Atom'>
<title>skiff.git/internal/envfile, 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-08-07T04:22:03Z</updated>
<entry>
<title>Add skiff config set/unset/list, backed by /app/env in the app's dataset</title>
<updated>2026-08-07T04:22:03Z</updated>
<author>
<name>Claude</name>
<email>noreply@anthropic.com</email>
</author>
<published>2026-08-07T04:22:03Z</published>
<link rel='alternate' type='text/html' href='https://git.mikeanthonywild.com/skiff.git/commit/?id=f34ba20fc566ab861179a8ac2fd55eaabbc6a327'/>
<id>urn:sha1:f34ba20fc566ab861179a8ac2fd55eaabbc6a327</id>
<content type='text'>
Config vars are plain env vars, injected into both the running app (via
rc.d) and the release phase, and versioned on the same ZFS snapshot
timeline as deploys - a bad config change gets the same automatic
snapshot/restart/health-check/rollback guarantee a bad deploy already
gets. Extracts deploy.go's health check into internal/health so both
paths share it.

Verified end-to-end against a FreeBSD VM: config set/unset, automatic
rollback on a health-check failure, and explicit `skiff rollback` all
correctly carry the env file along with the rest of the dataset.
</content>
</entry>
</feed>
