Duc-Tam Nguyen
b5f32b7b2b
Wrapping a packed viewer in a .app or .AppImage was its own --format app value, parallel to zim and binary. But an app is really just the binary format with a bundle around it, so a separate format meant duplicating the base/icon handling and made the three formats feel like an awkward choice. Turn it into a --app flag that builds on the binary format. It composes with --base (including a webview base) and --icon, while --format stays zim or binary. The bundle builders are unchanged; only the CLI surface moves.
4.7 KiB
4.7 KiB
title, description, weight
| title | description | weight |
|---|---|---|
| Release notes | What changed in each kage release. | 40 |
The authoritative, commit-level history lives in CHANGELOG.md and on the releases page. This page summarises each version.
Unreleased
Double-click apps, so a packed mirror opens like a real desktop app instead of a terminal program.
kage pack --appwraps the viewer in a double-click app with the site's favicon as its icon. The flag builds on the binary format, so it composes with--base(including awebviewbase) and--icon. On macOS that is a.appbundle; on Linux, with a Linux--base, an AppImage-style.AppDirthat becomes a single.AppImagewhenappimagetoolis installed. The icon is pulled from the mirror automatically, or set with--icon.- A GUI-subsystem Windows base ships in the release as
kage_<version>_windows-gui_<arch>.zip. Pack a viewer onto it with--format binary --baseand the resulting.exeopens with no console window behind it. - Smarter cross-platform packing. kage reads the base binary's executable header to detect its target OS, so a Windows viewer always gets a
.exename and the right run hint, regardless of how the base file is named.
v0.1.2
A security fix for how kage launches Chrome, clearer crawl errors, and a container image that actually runs.
- Chrome keeps its sandbox on by default. Earlier versions launched Chrome with
--no-sandboxon every run, which switched off the browser's main security boundary even on an ordinary desktop where the sandbox works fine (#10). The sandbox now stays on, and is dropped only where it genuinely cannot start: inside a container (detected fromIN_DOCKERor/.dockerenv) or when running as root. Whenever it is dropped, kage says so on stderr, so the choice is never silent. - Transient asset failures retry. A download that hits a 403/429, a 5xx, or a network blip is retried with a short backoff, which recovers files that bot-protection rejects on the first request of a burst. Permanent failures like a 404 are not retried.
- Clearer crawl errors. Each failure now logs a classified reason (
HTTP 403 Forbidden,timed out, ...), the URL, and the page that referenced it, and the end-of-run summary lists what went wrong instead of printing only a count. - The container image runs. Chrome aborted in the image with
chrome_crashpad_handler: --database is required, so the crash reporter is now disabled inside a container, and thekageuser has a writable home (the mounted/outvolume) so output, resume state, and Chrome's profile no longer fail with a permission error (#7).
v0.1.1
Packing, so a clone can travel as one file instead of a folder.
kage pack <mirror-dir>collapses a mirror into a single distributable file.--format zim(the default) writes an open ZIM archive, the same format Kiwix uses, so the file opens in any ZIM reader and not just kage.--format binaryappends that archive to a copy of kage to make a self-contained executable that serves the site offline when run. Packing is deterministic, so the same mirror produces a byte-identical file.kage open <file.zim>serves a packed ZIM back over a local HTTP server, the read side ofkage pack --format zim.- An optional native-window viewer. Built with
-tags webview,kage openand a packed binary show the site in a real window backed by the operating system's WebView instead of a browser tab. The default build stays pure Go and opens the browser, so the release pipeline is unchanged. - A pure-Go
zimpackage that reads and writes the ZIM format: a fixed header, MIME and pointer lists, zstd or stored clusters, redirects, and a trailing MD5.
v0.1.0
The first release. kage clones a live website into a self-contained folder you can browse offline, with every script stripped out.
kage clone <url>renders each page in headless Chrome, strips all JavaScript, and localises CSS, images, and fonts to relative paths.kage serve [dir]previews a cloned folder over a local file server.- Idempotent and resumable. Each page is keyed by the file it writes, so a page reached over http and https, or as
/index.htmlversus/, is fetched once. Re-running resumes;--refreshre-renders in place;--forcestarts clean. - Polite by default. Honours
robots.txt, seeds fromsitemap.xml, scopes to the seed host, and runs three parallel worker tiers. - Packaged everywhere. Archives,
.deb/.rpm/.apk, a multi-arch GHCR image with Chromium bundled, checksums, SBOMs, and a cosign signature.