Technique
Lynx Storage - ir.attachment Routing
Route Odoo attachments to S3 object storage with quota-aware fallback
lynx_storage_attachment
· v19.0.1.0.0
What this solves
Lynx Storage - Attachment Backend
Routes Odoo attachments through a pluggable storage backend - local disk, S3, MinIO, or any S3-compatible object store - so attachment storage scales independently of the Odoo filestore and survives container restarts.
Odoo's default ir.attachment storage uses the local filesystem, which limits horizontal scaling and ties attachment durability to volume backups. This module adds a backend abstraction so the same ir.attachment model can transparently store its bytes in S3 (or S3-compatible buckets like MinIO) while keeping the metadata in PostgreSQL.
Key Features
Pluggable backend - configurable per-company storage target.
S3 / MinIO support - any S3-compatible object store works without code changes.
Filesystem fallback - existing local-disk attachments continue to work.
Transparent reads - existing code reads ir.attachment.datas without changes.
Background migration - one-shot tool moves existing attachments to the new backend.
Per-company config - different companies can target different buckets in a multi-company install.
Integrates With
base - the ir.attachment model being extended.
Depends on
Try Lynx Storage - ir.attachment Routing on your team.
Free trial, no credit card. Talk to sales when you're ready.