A light-weight RSpec-esque testing framework
NodeSpec CLI - AI-friendly Node.js project scaffolding tool
Rendering math expressions in ProseMirror
JS API for Equilibrium and Genshiro parachains.
Generate a single OpenAPI v3 spec from multiple sources
The canonical Codama node specification and meta-model
This repo demonstrates how [ProseMirror] could be used to build a visual editor for [Govspeak].
Javascript based mindmap library. It provides dragging, aligment, styling(node, edge) and editing functionality.
Pure configuration presets for Deepractice Node.js projects
Runtime API for Cucumber BDD step definitions and hooks
Testing utility functions for Deepractice Node.js projects
Capacity Model - Node specification and capacity planning for GeoMind/Mycelium
Mycelium - Distributed infrastructure components for GeoMind
Fast schema-agnostic parser and manipulator for Tiptap/ProseMirror JSONContent documents
Declarative media processing pipeline DSL — typed filter graph, node composition, and execution planning for OxiMedia
不可变数据结构与事务系统基础
Distributed AI Swarm Runtime
Ezu Style Spec: declarative style specification for painterly map rendering
Derive macros for JSON Schema generation and HeroScript serialization
Derive macro to generate JSON Schema from Rust structs
Embedded graph database with full ACID transactions, HNSW vector search, dual backend support, and comprehensive graph algorithms library
An acoustic echo canceller written in rust based on the WebRTC aec3 project
The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.42) is used. For example, calling `/info` is the same as calling `/v1.42/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```