📄️ Configuring ApertureDB
ApertureDB reads server settings from a JSON configuration file. The -cfg flag specifies its path:
📄️ Deployment
ApertureDB deployment packages run the database and its supporting services on a Docker host or Kubernetes cluster. Docker Compose, Helm, and OpenTofu packages are published on Docker Hub; each fits a different infrastructure workflow.
📄️ Deprecations
This page lists compatibility behavior and changes that affect existing applications and deployments. The command reference and examples describe the current API. The lists below distinguish compatibility syntax that still works from features that have been removed. GetApiSchema favors current spellings: it omits DiagnosticTool, deprecated result selectors, and legacy constraint syntax. Some compatibility fields, including GetStatus.cpu_utilization, remain in the schema. Schema presence alone does not establish that a field is recommended or fully implemented; use the command reference and migrations below.
🗃️ Deployment guides
3 items
📄️ ReleaseNotes
Customer-facing changes in ApertureDB, starting with version 0.19.7. Releases are listed newest first. Links point to the current documentation; older releases may use different parameters or response formats. For deprecated features, removed syntax, and upgrade instructions, see Deprecations and migrations.
📄️ Distributed ApertureDB
In this section, we describe
📄️ Enterprise Features
Monitoring and Logging
📄️ Frequently Asked Questions
ApertureDB manages media, feature vectors, and associated metadata through a
📄️ Troubleshooting
A query failure is identified by its status, info, and failing command.