mirror of
https://github.com/camptocamp/odoo-cloud-platform.git
synced 2026-06-23 18:04:34 +00:00
Guewen Baconnier
53d7cdf3e7
Because it provokes serialization errors during the installation or update of addons. Do not commit as we might commit unwanted things... Later, we might want to add a specific, more elaborate, migration process.
Attachments on S3 storage ========================= This addon allows to store the attachments (documents and assets) on S3 or any other S3-compatible Object Storage. Configuration ------------- Activate S3 storage: * Create or set the system parameter with the key ``ir_attachment.location`` and the value in the form ``s3``. Configure accesses with environment variables: * ``AWS_HOST`` (not required if using AWS services) * ``AWS_ACCESS_KEY_ID`` * ``AWS_SECRET_ACCESS_KEY`` * ``AWS_BUCKETNAME`` Read-only mode: The bucket and the file key are stored in the attachment. So if you change the ``AWS_BUCKETNAME`` or the ``ir_attachment.location``, the existing attachments will still be read on their former bucket. But as soon as they are written over or new attachments are created, they will be created on the new bucket or on the other location (db or filesystem). This is a convenient way to be able to read the production attachments on a replication (since you have the credentials) without any risk to alter the production data. This addon must be added in the server wide addons with (``--load`` option): ``--load=web,web_kanban,attachment_s3`` Limitations ----------- When the ``ir.attachment`` model is started, it will automatically migrate the attachments which are not stored in S3 yet. This might be an issue when the number of attachments is huge. In that case, you might have more control by calling yourself ``env['ir.attachment'].force_storage()``.