Align docs, examples, the setup wizard, and telemetry tests with the
current Doubao multimodal embedding model so generated configs keep
referencing the supported default consistently.
* docs: fix docker deployment
* reorg: remove third_party/agfs
* feat(s3fs): add disable_batch_delete option for OSS compatibility
Port of PR #1333 from Go version to Rust:
- Add disable_batch_delete config option to S3Client
- When enabled, use sequential single-object deletes instead of DeleteObjects
- This is for S3-compatible services like Alibaba Cloud OSS that require
Content-MD5 for DeleteObjects but AWS SDK v2 does not send it by default
- Add documentation and config example for OSS
* fix(s3fs): pass disable_batch_delete config from Python to Rust
Add disable_batch_delete to the s3_plugin_config dict in _generate_plugin_config
so that the Python config can properly control the Rust S3FS plugin's behavior.
* reorg: remove third_party/agfs
* reorg: remove third_party/agfs
* change some docs
* change some docs
---------
Co-authored-by: openviking <openviking@example.com>
The Helm chart shipped with OpenAI as the default model provider but
OpenViking is a volcengine project. Switch embedding/vlm defaults to
doubao series, add the required root_api_key field, add missing
storage.vectordb/agfs config sections, and guard against replicaCount>1
which causes RocksDB lock contention on a single PVC.
Closes#724
Adds a complete Helm chart at deploy/helm/openviking/ with:
- Deployment with Recreate strategy (RocksDB single-writer)
- PVC for persistent data storage
- ConfigMap for ov.conf configuration
- Optional ingress support
- Health probes matching Dockerfile HEALTHCHECK
- Configurable resources, replicas, and all ov.conf settings
- Installation guide at deploy/helm/README.md
Zayn Jarvis