Tosone
7039914b3a
The repository pages carried their own tab strip, and the sidebar repeated the same entries under the repository node, so the same navigation existed in two places and neither was complete: the Setup builder page was only reachable from the code repository list, which no longer links to it. - add /namespaces/:namespace/repository/builder rendering the setup builder, and turn the repository tabs into Summary | Builder | Runs | Tag list; the former "Builder" tab, the runner list, becomes "Runs" - remove the repository level from the sidebar: its entries are the page tabs now, and "Repository list" stays highlighted while browsing into a repository - drop NamespaceTabs, the duplicate header strip on the namespace pages - resolve entity ids as opaque UUID strings: interface fields are strings now and the pages that parsed ids with parseInt stopped truncating them (a UUIDv7 starts with "1a1...", so parseInt returned 1) - add useNamespaceId: a page opened without ?namespace_id — a bookmark or a hand written URL — looks the id up from the namespace in the route instead of requesting /namespaces/null or /namespaces// - the tag page: title is Tags, its search box matches the namespace one, and it skips the request while the namespace is unresolved Verification: - cd web && npx tsc --noEmit - cd web && npx oxlint - cd web && npx vite build
sigma
Sigma is an image registry that is extremely easy to deploy and maintain, and it adheres to the interface standards defined by the OCI Distribution Specification 1.1, it can also support any other client programs that follow the interface definition of the OCI Distribution Specification, such as oras, apptainer, helm, and nerdctl.
Quick Start
Now you can use this command to run a simple server:
docker run --name sigma -p 3000:3000 --rm tosone/sigma:nightly-alpine
The default username and password is: sigma/Admin@123. If you want to modify the default password, please refer to the configuration instructions.
Demo Server
It is deployed on an AWS EC2 instance (2C4G, 40G disk) running Debian 12.1 as the Linux distribution. The Docker version used is 25.0.3. The demo server was set up following these instructions.
Visit: https://sigma.tosone.cn, username/password: sigma/Admin@123
Architecture
The diagram below maps Sigma's main runtime layers, from client entry points to request handling, background workers, and the infrastructure services they depend on.
Features
- Support docker registry v2 protocol.
- Support OCI Image v1 Format and OCI Image Index v1 Format.
- Support OCI artifacts such as helm and so on.
- Support OCI sbom.
- Support Image security scan.
- Support registry proxy.
- Support Namespace quota.
- Support Image automatic garbage collection.
- Support Image sign.
- Support Image build in docker, podman and kubernetes.
- Support Image replication.
AI Clients and Automation
Sigma provides two integration paths for AI clients and external automation:
sigma-cli: a single binary that operates a remote Sigma server over the REST API. It covers namespaces, repositories, tags, artifacts, members, and users. See CLI & AI Agents.- External REST API skill:
tools/skill/sigma-api-operatorpackages a reusable skill andswagger.yamlso CLI agents such as Claude Code or Copilot CLI can discover Sigma APIs and operate resources through HTTP requests, including the areas the CLI does not wrap yet.