Skip to content

Releases

v0.1.16

Choose a tag to compare

@liustack liustack released this 22 Nov 01:02

tifa dev runs natively on Windows.

  • tifa dev on Windows (10 1809 and later, tested on Windows Server 2022 and 2025): the foreground server, --background, dev status, dev logs, dev stop and tifa errors. Ctrl-C, closing the console window and tifa dev stop stop it, the app runs OnShutdown on each restart, and a tifa dev killed 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 build in an app that is building already now stops with an error, as on Linux and macOS.

Full list: CHANGELOG

v0.1.15

Choose a tag to compare

@liustack liustack released this 21 Nov 22:27

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 check and tifa build run on Windows 10 1809 and later (tested on Windows Server 2022 and 2025). A build for Windows writes bin\<name>.exe. tifa dev on Windows comes in a later release.
  • import.meta.env.BASE_URL is / under tifa 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 setup says 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 Intl on very long inputs.
  • A built program serves .js as text/javascript on every system.

Full list: CHANGELOG

v0.1.14

Choose a tag to compare

@liustack liustack released this 21 Nov 17:45

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_HOST is now TIFA_DEPLOY_HOST, CF_CACHE_PURGE_TOKEN is TIFA_DEPLOY_CF_PURGE_TOKEN, CF_ZONE_ID is TIFA_DEPLOY_CF_ZONE_ID. An old name left in .env stops tifa deploy with an error that names the new one.
  • Renamed workflow secrets. tifa deploy setup finds 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 a cf login can clear the CDN cache at deploy.
  • No gh needed. Without gh, setup and remove call the GitHub API with a fine-grained token from TIFA_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

Choose a tag to compare

@liustack liustack released this 21 Nov 14:37

Deploys no longer put the server where a public repository shows it.

  • deploy.host is gone from tifa.yaml. tifa deploy reads the server from --host, the environment variable DEPLOY_HOST, or DEPLOY_HOST in the app's .env: an ssh alias or ssh://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.cdn is deploy.front again.
  • tifa new pins github.com/liustack/sqlite v0.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

Choose a tag to compare

@liustack liustack released this 21 Nov 07:34

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 logs prints the log of the app on the server. -n for more lines, -f to follow until Ctrl-C.
  • tifa deploy status shows the release that runs and its commit, the releases kept, since when the service runs, what /healthz answers and the memory of the program.
  • tifa deploy remove takes 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.yaml is a warning at its line, and GitHub Actions marks that line.

Full list: CHANGELOG

v0.1.11

Choose a tag to compare

@liustack liustack released this 21 Nov 01:29

Findings of Tifa now show up on the files of a GitHub run and pull request.

  • Marks in GitHub Actions. tifa check, tifa build and tifa gen mark 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. The ci.yml of tifa new and the deploy workflow of tifa deploy setup leave the checks to tifa check. An app made before gets the marks by adding --ignore-scripts to the pnpm install line of its .github/workflows/ci.yml.

Full list: CHANGELOG

v0.1.10

Choose a tag to compare

@liustack liustack released this 20 Nov 19:26

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 (--all lists 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.front is now deploy.cdn. Same values, none and cloudflare. The old key stops deploy and setup with the new name. Rename front: to cdn: under deploy: in tifa.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 Cache can stay old on the CDN for up to its Cache time. tifa deploy setup --cache-purge-token adds or replaces it.
  • Tailscale. With deploy.ssh: tailscale, setup asks for your OAuth client, checks it, and keeps it. --tailscale-oauth replaces it.
  • Setup never tells you to run gh yourself.

Full list: CHANGELOG

v0.1.9

Choose a tag to compare

@liustack liustack released this 20 Nov 14:19
  • Fixed: behind Cloudflare, browsers kept pages with Cache and the files of public/ for 4 hours, because the zone's Browser Cache TTL replaced their max-age=0 and no-cache, and no purge reaches a browser. The cache rule tifa deploy setup writes now keeps the browser TTL of the origin. Upgrading: run go tool tifa deploy setup again. With your own Cloudflare rules, set Browser TTL to "Respect origin TTL".
  • Added: tifa build and tifa dev warn when page source names an image or font of public/ 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

Choose a tag to compare

@liustack liustack released this 20 Nov 12:11

The deploy section of tifa.yaml is now three plain questions, and setup is faster.

  • deploy.front: cloudflare puts Cloudflare in front of the host of site.url (Tunnel, DNS, cache rules, cache clearing). deploy.domain is gone.
  • deploy.ci: github replaces deploy.github: true. deploy.ssh stays.
  • 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 setup reads 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

Choose a tag to compare

@liustack liustack released this 20 Nov 09:40

tifa deploy now works from the deploy section of tifa.yaml, from your machine or from GitHub Actions.

  • Four settings: host, domain, ssh (direct, cloudflare or tailscale) and github. go tool tifa deploy setup shows 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 the CI workflow passes, and sets the repository secrets with gh. CI can reach SSH directly, through a Cloudflare Tunnel guarded by Access, or over Tailscale.
  • With domain set, deploy and rollback clear the Cloudflare cache of that host name once the release is live.
  • go tool tifa deploy env set/unset/list edits the app's .env on the server and restarts it with a health check.
  • go tool tifa new writes a GitHub CI workflow that runs go tool tifa check.
  • tifa deploy github and setup --cloudflare are gone: set deploy.github and deploy.domain instead. The deploy commands are still marked as may change.

Full list: CHANGELOG