Repository navigation
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