Design archive — not shipped
This page describes a future or historical network, API, P2P, or deployment surface. The current product is a local alpha; there is no working network transfer, hosted server, public API/SDK, or deployable service.
Design Archive
Container Packaging Boundary
A source-built local CLI image is different from a supported hosted-service deployment.
Design, not a shipped service
The current product is a local alpha CLI and library. There is no hosted Dits service, complete repository remote, public API or SDK, managed webhook system, official server image, or supported production deployment. The items below are conditional design targets, not setup instructions or commitments.
Status
The source tree contains a Dockerfile that builds the local CLI for a Linux x64 runtime. Dits does not publish an official image, server image, registry release, production Compose stack, or container support contract. The CLI image does not add working remotes or a hosted API.
Possible design targets
- Signed, provenance-attested images for an explicitly supported architecture matrix.
- Separate local CLI packaging from any future stateful server and worker images.
- Non-root execution, immutable configuration, health checks, upgrade policy, and persistent-state documentation.
Prerequisites before implementation claims
- A maintained server implementation before server-container documentation can exist.
- Automated image builds, vulnerability scanning, smoke tests, and release retention.
- Documented volume ownership, backup, migration, rollback, and resource requirements.
What can be evaluated today
- Build the repository Dockerfile locally if a source-built CLI container suits a disposable evaluation.
- Mount only backed-up test data and verify host-file ownership after container use.
- Use the npm binaries on their two packaged targets or build the CLI directly from source.