Artifact 5b187c9dafcc0de01aaebec24b6f2b35d89daa8a5a0a8a9fd89e5dc7621085ef:
- File
docs/site/content/docs/get-started/install.md
— part of check-in
[b451efa274]
at
2026-10-31 16:23:44
on branch main
— docs: the libfossil_noslog tag, and how the publisher engine gets smaller still
The TinyGo section of the install guide and examples/tinygo described libfossil_nohttp but not libfossil_noslog, which only the changelog mentioned. Both now say what the tag leaves out and what changes.
The install guide gains a "Smaller still" section pointing at the html-artifact-publisher engine's build: no scheduler, a reactor export, explicit panic unwinding and a patched standard library, with the behavior the patch changes. It says plainly that these steps are the publisher's and that this repository does not build that way.
CI never compiled the code behind either tag, so a change could break a tagged embedder unnoticed until the publisher's CI ran against a release. A new build-size-tags job builds the library under both tags, vets the repository under libfossil_noslog, and runs the check-in linker's tests under it. (user: [email protected], size: 5651) [annotate] [blame] [check-ins using] [more...]
title: Install
weight: 10
go-libfossil is a Go module and a command. Neither needs cgo, a C toolchain or an installed fossil.
The command
go install github.com/danmestas/go-libfossil/cmd/libfossil@latest
libfossil --help
This needs the Go toolchain named in go.mod (Go 1.26 or later). The binary is statically linked and runs on Linux, macOS and Windows. Every command is listed in the CLI reference.
The library
go get github.com/danmestas/go-libfossil@latest
The library talks to SQLite through database/sql and does not pick a driver for you. Blank-import exactly one of the two driver modules in your main package; importing both panics at start-up.
| Driver | Import | Use it for |
|---|---|---|
| modernc | _ "github.com/danmestas/go-libfossil/db/driver/modernc" |
servers, command-line tools, desktop: SQLite translated to Go |
| ncruces | _ "github.com/danmestas/go-libfossil/db/driver/ncruces" |
GOOS=js and GOOS=wasip1 builds: SQLite itself as WebAssembly |
Each driver is its own module, so go get it too:
go get github.com/danmestas/go-libfossil/db/driver/modernc@latest
WebAssembly
With the ncruces driver the module builds for GOOS=js GOARCH=wasm (a browser) and GOOS=wasip1 GOARCH=wasm (any WASI Preview 1 host). CI builds the module's packages for js/wasm on every change. The wasm example builds and runs a WASI module.
TinyGo
The whole public API, the HTTP sync client and signing included, also builds with TinyGo for the wasm target, which is what makes it small enough to ship with a page or an edge function:
tinygo build -target=wasm -no-debug -opt=z -stack-size=1MB -o libfossil.wasm ./examples/tinygo/
wasm-opt -Oz --detect-features --strip-debug --strip-producers libfossil.wasm -o libfossil.wasm
- Size: for
examples/tinygo, about 1.3 MB gzipped as CI builds it, against about 4.1 MB from the standard toolchain. A program without sync is smaller. - Driver: a TinyGo build imports no SQLite driver. The host registers a
database/sqldriver over its own SQLite; ncruces is for standard Go builds and modernc has no wasm build. - Stack:
-stack-size=1MB, because TinyGo's default goroutine stack is too small for the deeper paths. - Differences: under TinyGo a sync redirect ends the request with an error instead of being followed, and DNS failures are not classified as transient.
- Without HTTP: a program that serves sync through
HandleSyncWithOptsand syncs, if at all, through aTransportits host supplies can build with-tags libfossil_nohttp. That leaves outNewHTTPTransport,WithHTTPClient,Repo.Pull,Repo.XferHandlerandRepo.ServeHTTP, and with themnet/http, whose TLS and X.509 dependencies are about 97 KB of a gzipped TinyGo binary. Everything else is unchanged. The tag is for library embedders: theclipackage andexamples/tinygo, which callsNewHTTPTransport, do not build with it. A tagged embedder supplies its own transport and serving, for example aTransportforSyncand its own request handling aroundHandleSyncWithOpts. - Without slog:
-tags libfossil_noslogleaveslog/slogout, about 33 KB of a gzipped TinyGo binary. The check-in linker then writes its info and warning messages to stderr as plainLEVEL message key=valuelines and drops its debug messages; nothing else changes. It combines withlibfossil_nohttp.
CI builds examples/tinygo with TinyGo 0.43 on every change, and builds the library under both tags.
Smaller still
The html-artifact-publisher engine, which serves Fossil repositories from Cloudflare Durable Objects, uses both tags and goes further. It is 754,725 bytes gzipped with TinyGo 0.43 and Go 1.27.3, where the same program built as above is about 1.2 MB; in the publisher's measurements on Go 1.26 it also ran its test workload about three times faster. Its fossil/build.sh is the worked example. Beyond the tags it:
- builds with
-scheduler=none, which drops TinyGo's asyncify pass, the largest single cost; - builds as a reactor (
-buildmode=c-shared) and exports its entry point with//go:wasmexport, because ajs.FuncOfcallback cannot run without a scheduler; - adds
-panic-unwind=explicit, sorecoverstill works without asyncify; - compiles against a patched copy of the Go standard library (
fossil/goroot.patch) that removes the goroutinesdatabase/sql,contextandtime.AfterFuncstart, since a build without a scheduler cannot run them. The patch changes behavior:database/sqlopens connections on demand and does not watch contexts, a context derived from a custom parent does not inherit its cancellation, and anAfterFunccallback runs inline. It also leaves out the FIPS self-tests.
These steps are the publisher's, not the library's, and this repository's CI does not build that way. They hold for a program that, like the publisher's engine, opens repositories, commits and serves sync through HandleSyncWithOpts; other paths, such as the HTTP sync client, may start goroutines of their own that such a build cannot run.