Tosone
64e4de5702
The form mixed three interaction styles: popovers with a cmdk search list, plain selects and hand-styled inputs. Picking a provider could leave two options looking highlighted, an empty list opened an empty popup that rendered as a thin grey line, and several fields had no dark mode support. Make every picker a Select and calm the form down: - provider, organization, repository and branch — plus the cron and merge branch pickers — are Selects now; the popup is only rendered when there is something to choose, and the branch pickers refresh their list when opened because branches are no longer synced - provider options show their display name, an unavailable provider disables the organization and repository pickers, and its hint opens the credential dialog in place instead of navigating away - the OCI repository picker lists the repository name without the namespace prefix, the way the repository is referred to elsewhere - the section descriptions move into info tooltips next to the headings - clone depth uses the shared input, round-trips through code_repository_clone_depth, clamps to a non-negative integer and explains that 0 clones the full history - the self-managed repository block uses the shared inputs, keeps the token masked and gives the fields room to breathe - CommandItem gets a pointer cursor, which fixes every cmdk list, and the setup page drops the forced 100rem width that pushed it past the viewport 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.