Repository navigation
Releases
v0.1.16
tifa dev runs natively on Windows.
tifa devon Windows (10 1809 and later, tested on Windows Server 2022 and 2025): the foreground server,--background,dev status,dev logs,dev stopandtifa errors. Ctrl-C, closing the console window andtifa dev stopstop it, the app runsOnShutdownon each restart, and atifa devkilled in the Task Manager takes Node, Vite and the app with it. On Windows lists what differs there. No WSL needed.- On Windows a second
tifa buildin an app that is building already now stops with an error, as on Linux and macOS.
Full list: CHANGELOG
v0.1.15
tifa new, tifa check and tifa build run natively on Windows, and a batch of fixes from building tifago.com with Tifa.
- Windows.
tifa new,tifa checkandtifa buildrun on Windows 10 1809 and later (tested on Windows Server 2022 and 2025). A build for Windows writesbin\<name>.exe.tifa devon Windows comes in a later release. import.meta.env.BASE_URLis/undertifa dev, as in a build. Libraries that build app URLs from it, such as the search of Fumadocs, now work in dev.- lucide-react 1.75 and later get the icon cache again, and the build no longer warns about them.
- Quieter builds. Rolldown's plugin timing notes are off, and the size warning for the client entry starts at 1000 kB. Settings the app gives in its own Vite config win.
tifa deploy setupsays in its plan what it does not know yet, instead of showing a random name it will not use, a cut tunnel name or ssh's raw error.- llms.txt names a home page with no title after the site.
- Server rendering runs on slowjs v0.31.11. The render timeout, the stop on shutdown and the memory limit now also hold inside
Intlon very long inputs. - A built program serves
.jsastext/javascripton every system.
Full list: CHANGELOG
v0.1.14
tifa deploy names every input and secret with TIFA_DEPLOY_, reads every input the same way (flag, then environment, then .env), and sets up CI without gh.
- Renamed inputs.
DEPLOY_HOSTis nowTIFA_DEPLOY_HOST,CF_CACHE_PURGE_TOKENisTIFA_DEPLOY_CF_PURGE_TOKEN,CF_ZONE_IDisTIFA_DEPLOY_CF_ZONE_ID. An old name left in.envstopstifa deploywith an error that names the new one. - Renamed workflow secrets.
tifa deploy setupfinds the secrets an earlier version set, sets them under the new names and removes the old ones. - Purge token and zone ID from
.env. A machine without acflogin can clear the CDN cache at deploy. - No gh needed. Without gh,
setupandremovecall the GitHub API with a fine-grained token fromTIFA_DEPLOY_GITHUB_TOKEN. Setup prints a link that opens GitHub's token form with the permissions filled in.
Upgrading: rename the inputs in .env, run go tool tifa deploy setup again when deploying from CI, and commit the workflow it writes.
Full list: CHANGELOG
v0.1.13
Deploys no longer put the server where a public repository shows it.
deploy.hostis gone fromtifa.yaml.tifa deployreads the server from--host, the environment variableDEPLOY_HOST, orDEPLOY_HOSTin the app's.env: an ssh alias orssh://host[:port].- The generated GitHub workflow no longer writes the ssh port or the Cloudflare zone ID: both live in secrets, and the host is masked in the Actions log.
- With
ssh: cloudflare, the ssh host name has a random part, and CI installs a pinned, checksummed cloudflared. deploy.cdnisdeploy.frontagain.tifa newpinsgithub.com/liustack/sqlitev0.1.8.
Apps that deploy with Tifa must move deploy.host to .env, rename cdn: to front:, and run go tool tifa deploy setup again when they deploy from CI. See the changelog.
v0.1.12
After a deploy, you no longer need to log in to the server to see how the app is doing or to take it down.
tifa deploy logsprints the log of the app on the server.-nfor more lines,-fto follow until Ctrl-C.tifa deploy statusshows the release that runs and its commit, the releases kept, since when the service runs, what/healthzanswers and the memory of the program.tifa deploy removetakes the app off the server and takes back what Tifa made for it in Cloudflare and GitHub. It prints a plan first and asks you to type the name of the app.- A retired key in
tifa.yamlis a warning at its line, and GitHub Actions marks that line.
Full list: CHANGELOG
v0.1.11
Findings of Tifa now show up on the files of a GitHub run and pull request.
- Marks in GitHub Actions.
tifa check,tifa buildandtifa genmark each of their findings on its file and line, once, as an error or a warning. Findings in TypeScript files were not marked before, and a warning about a Go file was marked as an error. - New CI files install with
--ignore-scripts. Theci.ymloftifa newand the deploy workflow oftifa deploy setupleave the checks totifa check. An app made before gets the marks by adding--ignore-scriptsto thepnpm installline of its.github/workflows/ci.yml.
Full list: CHANGELOG
v0.1.10
tifa deploy setup asks less and says only what matters.
- Short plan. Setup lists only what it will add, change or remove, counts what is already right (
--alllists it), and ends with a numbered list of what it cannot do for you. When everything matches it prints one line. It exits with an error when something is left for you. deploy.frontis nowdeploy.cdn. Same values,noneandcloudflare. The old key stops deploy and setup with the new name. Renamefront:tocdn:underdeploy:intifa.yaml.- The cache purge token is optional. Setup asks for it on the first CI setup only. Without it a deploy still works, and a page with
Cachecan stay old on the CDN for up to itsCachetime.tifa deploy setup --cache-purge-tokenadds or replaces it. - Tailscale. With
deploy.ssh: tailscale, setup asks for your OAuth client, checks it, and keeps it.--tailscale-oauthreplaces it. - Setup never tells you to run
ghyourself.
Full list: CHANGELOG
v0.1.9
- Fixed: behind Cloudflare, browsers kept pages with
Cacheand the files ofpublic/for 4 hours, because the zone's Browser Cache TTL replaced theirmax-age=0andno-cache, and no purge reaches a browser. The cache ruletifa deploy setupwrites now keeps the browser TTL of the origin. Upgrading: rungo tool tifa deploy setupagain. With your own Cloudflare rules, set Browser TTL to "Respect origin TTL". - Added:
tifa buildandtifa devwarn when page source names an image or font ofpublic/by path. Import it instead, so it gets a hashed name and a one-year cache.public/is for files that must keep their name, see Static files. - Changed: new apps ignore
.cloudflare/, where cf remembers the account.
Full list: CHANGELOG
v0.1.8
The deploy section of tifa.yaml is now three plain questions, and setup is faster.
deploy.front: cloudflareputs Cloudflare in front of the host ofsite.url(Tunnel, DNS, cache rules, cache clearing).deploy.domainis gone.deploy.ci: githubreplacesdeploy.github: true.deploy.sshstays.- Setup asks you to paste a cache purge token made from a prefilled Cloudflare form, checks it, and stores it as the GitHub secret
CF_CACHE_PURGE_TOKEN, so deploys from GitHub Actions clear the CDN cache. tifa deploy setupreads in parallel and shows progress: planning went from 49 s to 7 s on a slow link.
Upgrading: replace deploy.domain: X with site.url: https://X and deploy.front: cloudflare, replace deploy.github: true with deploy.ci: github, then run go tool tifa deploy setup.
Full list: CHANGELOG
v0.1.7
tifa deploy now works from the deploy section of tifa.yaml, from your machine or from GitHub Actions.
- Four settings:
host,domain,ssh(direct,cloudflareortailscale) andgithub.go tool tifa deploy setupshows a plan of what it will add, change or remove on the server, Cloudflare and GitHub, asks, then applies it. It removes only what Tifa made. - With
github: true, setup writes.github/workflows/tifa-deploy.yml, which deploys after theCIworkflow passes, and sets the repository secrets with gh. CI can reach SSH directly, through a Cloudflare Tunnel guarded by Access, or over Tailscale. - With
domainset, deploy and rollback clear the Cloudflare cache of that host name once the release is live. go tool tifa deploy env set/unset/listedits the app's.envon the server and restarts it with a health check.go tool tifa newwrites a GitHub CI workflow that runsgo tool tifa check.tifa deploy githubandsetup --cloudflareare gone: setdeploy.githubanddeploy.domaininstead. The deploy commands are still marked as may change.
Full list: CHANGELOG