acelith/Chronexus-Server
1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions

2 releases 2 tags

RSS feed
  • v0.1.1 0e8faf1772

    Chronexus Server 0.1.1
    Some checks failed
    Server checks / check (push) Has been cancelled
    Details
    Server checks / audit (push) Has been cancelled
    Details
    Stable

    acelith released this 2026-10-27 12:44:58 +00:00 | 5 commits to main since this release

    Chronexus Server 0.1.1

    A maintenance release of the self-hosted companion of Chronexus, and the first one shipped as
    container images in the Forgejo registry for Linux amd64 and arm64.

    Install from the registry (no build needed):

    cp .env.example .env     # set CHRONEXUS_DOMAIN and CHRONEXUS_IMAGE=git.moix.me/acelith/chronexus-server:0.1.1
docker compose pull
docker compose --profile https up -d
docker compose exec -T server chronexus-server invite

    Fixed

    • The bundled HTTPS profile never started: Docker could give the server the address reserved
      for the proxy. Dynamic addresses now come from 172.30.253.128/25
      (CHRONEXUS_NETWORK_DYNAMIC_RANGE).
    • backup and verify failed 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.

    Assets: container images git.moix.me/acelith/chronexus-server:0.1.1 (linux/amd64,
    linux/arm64), the chronexus-server binaries for both Linux architectures (glibc, Debian 12)
    extracted from those images, and SHA256SUMS.txt.

    Image digest: git.moix.me/acelith/chronexus-server@sha256:ce86254ece7a62e1e619184ce982ee73fe36a725028f0fe44e91d9dbe15bedb5

    Downloads
  • v0.1.0 77848208c6

    Chronexus Server 0.1.0
    Some checks failed
    Server checks / check (push) Has been cancelled
    Details
    Server checks / audit (push) Has been cancelled
    Details
    Stable

    acelith released this 2026-10-26 18:39:43 +00:00 | 16 commits to main since this release

    Chronexus Server 0.1.0

    The first release of the optional, self-hosted companion for Chronexus 0.9.0 and later. It is
    Apache-2.0 licensed, offline-first for the desktop (the app works without it), and keeps your
    campaigns on a machine you control. No telemetry, no cloud AI, no third-party service.

    What it does

    • Invitation-only accounts (Argon2id, hashed tokens, persistent attempt limits, device sessions).
    • Campaigns with owner, player and reader roles, one-use invitations, versioned memberships.
    • Private-by-default content: pages, sessions, relationships, party members, selected character
      sheet sections and managed images (PNG/JPEG/WebP, original bytes, checksums).
    • Continuous replication for the desktop: incremental sync with fail-closed cursors, idempotent
      writes with verifiable request IDs, content-free change notifications, conflicts returned with
      both versions.
    • Revocation and deletion: removing a member, deleting your server copy, deleting a campaign (by
      its exact name) or your account; former members are told, nothing local is touched.
    • Operations: invite, recover, revoke-sessions, compact, backup, verify, restore,
      automatic pre-upgrade copies, health checks, a generated OpenAPI contract.

    Run it: copy .env.example to .env, set CHRONEXUS_DOMAIN, then
    docker compose --profile https up -d --build (bundled HTTPS) or docker compose up -d --build
    behind your own proxy. See docs/INSTALLATION.md.

    Verified (Windows x64, Rust 1.99.1): 71 integration tests (authorization matrix over every
    campaign route, hostile inputs, backup/restore and failed-upgrade recovery, lifecycle, sync and
    notifications), rustfmt, Clippy with warnings denied, a locked release build and the OpenAPI drift
    check; the real Chronexus 0.9.0 client engine ran against this server over loopback HTTP
    (two computers aligned with about 160 ms median latency, server restart recovery, conflicts,
    revocation, deletion, shared images and sections).

    Not verified, so not claimed: the Docker image and the compose files (Docker was unavailable:
    no image is published and the compose/Caddy files were only reviewed), Linux and macOS, ARM64, a
    real TLS deployment, vulnerability scans of dependencies and images, third-party penetration
    testing, and load beyond the built-in limits.

    Assets: the Windows x64 executable built from the tagged source, with its SHA-256. Other
    platforms: build from source with the pinned toolchain in docs/DEVELOPMENT.md.

    Downloads