Repository navigation
Chronexus Server 0.1.1
Chronexus Server 0.1.1
A maintenance release of the self-hosted companion of Chronexus, and the first one shipped as
Linux amd64 and arm64 container builds. The historical registry publication predates the GitHub migration; GHCR publication is pending.
Build from source:
cp .env.example .env # set CHRONEXUS_DOMAIN
docker compose --profile https up -d --build
docker compose exec -T server chronexus-server inviteFixed
- The bundled HTTPS profile never started: Docker could give the server the address reserved
for the proxy. Dynamic addresses now come from172.30.253.128/25
(CHRONEXUS_NETWORK_DYNAMIC_RANGE). backupandverifyfailed on macOS hosts (temporary directory behind a symbolic link).- Two verifications running at the same moment could lock each other's reference file.
- The published OpenAPI document now carries the Apache-2.0 licence.
Works with Chronexus 0.9.x and 0.10.0. Chronexus 0.10.0 adds member management (list,
change role, remove, leave) on top of the same API; no API change in this release.
Verified (27 October 2026): 75 integration tests on macOS arm64 (Rust 1.97), Clippy with
warnings denied, rustfmt, contract drift check; the Compose stack with the bundled Caddy over
HTTPS on Docker (linux/arm64); three real desktop apps (macOS and two Linux containers) passed a
37-step sharing scenario against it, including role changes, leaving, removal and a proxy outage;
an installed Linux release build signed in and downloaded a campaign over HTTPS. The images in
the registry were pulled back by digest and started.
Not verified: a public deployment with real DNS and certificates, a third-party
penetration test, image and dependency vulnerability scans, load testing. Data is not
end-to-end encrypted: the operator can read what users upload.
GitHub assets: the chronexus-server binaries for both Linux architectures (glibc, Debian 12), extracted from the historical container builds, and SHA256SUMS.txt.
Repository migration: GitHub is now the canonical source. The existing binaries and signatures were not rebuilt; their build source identifiers predate the authorized history rewrite.