5 Commits

Include renames

Author	SHA1	Message	Date
jcoffey-dev	4799d191a0	Fork tooling: a build check and a rename pass in the strip, a notice check in CI ... strip.py compiles the stripped tree, so a dual-licensed file that only serves an Enterprise feature fails the import instead of the merge, as v0.16.23's tests/src/directory/issuer.rs does. Upstream's tests of the features the fork rebuilt are expected not to compile there and are listed in build-check-known.txt; an error anywhere else fails the run. Checked against both imports: v0.16.22 passes with its 16 expected errors, v0.16.23 fails on issuer.rs alone. Imports the strip leaves unused are reported. It also renames the upstream name where clients, users or operators meet it as an identifier, from tools/fork/renames.py: wire-protocol names, the web interface's client id, store keys, configuration defaults and the served schema. main is renamed with the same module, so a re-import arrives purged and those lines don't conflict. notice-check.py fails CI when an upstream file the fork changed, measured against the upstream branch, lacks its AGPL 5(a) notice; --fix adds it. It runs beside the name check in a renamed fork-checks job. Also commits v0.16.23's strip report under docs/fork/strip-reports/, which the import in #18 left out.	2026-09-22 19:02:34 -07:00
jcoffey-dev	a4b091578d	CI: fail when the upstream name appears in a new string literal ... tools/fork/name-check.py reads every string literal in crates/ (comments and test directories skipped) and fails on any that carries the upstream name without an entry in name-allowlist.txt. An upstream merge can bring such strings in without a conflict, so it runs on every push and PR. The first run found three the earlier sweeps missed, fixed here: the SMTP HELP reply pointed at upstream's website (now brand_url!), the event collector thread was named after upstream, and the FreeBSD default data path still said /var/db/stalwart/ where Linux already had /var/lib/inbuxa/. Two operator-visible defaults are allowlisted as open, pending a decision: the log file prefix and the SQL stores' default database and user.	2026-09-22 16:12:47 -07:00
jcoffey-dev	b37d252660	ci: raise the Cargo target-dir limit to 60 GB ... The dev and test profiles together already take ~22 GB after one cold build, so the 25 GB limit would have wiped a warm cache within a build or two.	2026-09-22 08:45:15 -07:00
jcoffey-dev	1ee2e2a6a3	ci: persistent Cargo cache, run on either runner ... The build now mounts the named volume inbuxa-server-cargo at /cache and keeps CARGO_HOME and CARGO_TARGET_DIR there, so a push reuses the compiled dependency tree (RocksDB included) instead of rebuilding it from scratch. Both runners allow that one volume; each host keeps its own copy. With the cache in place the job moves to runs-on: light, so it can run on host2 as well. Cargo's parallelism now follows the job's CPU cap rather than the host's core count, and the target dir is dropped past 25 GB.	2026-09-22 07:59:35 -07:00
jcoffey-dev	29bcfecb80	ci: add Gitea Actions workflow ported from .gitlab-ci.yml	2026-09-21 22:45:05 -07:00