| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 294 |
| Technical Name |
gcs_filestore |
| License | OPL-1 |
Google Cloud Filestore
Move your Odoo attachments off the local disk and into a Google Cloud Storage bucket — transparently, with one-click sync and a clean configuration screen.
Key Features
- Transparent storage — new attachments (
ir.attachment) are written straight to your GCS bucket. - Test Connection — validate the credentials and bucket before activating.
- Sync to Bucket — upload your existing local filestore to GCS in one click.
- Sync to Local — bring files back to the local filestore whenever you need.
- Free local disk — optionally delete the local copy after upload.
- Safe by design — if GCS is ever unreachable, reads fall back to the local filestore.
- Clean Odoo 19 code — uses the modern raw-bytes storage API (no legacy base64 hacks).
How It Works
- Open Settings → Google Cloud Storage → Configurations and create a configuration.
- Fill in the Project ID, Bucket Name, Location and upload the Service Account JSON.
- Click Test Connection to verify access to the bucket.
- Turn on Active — from now on, new attachments are stored in GCS.
- Click Sync to Bucket to move your existing files. Use Sync to Local to reverse it.
Screenshots
1. Find it under Settings → Google Cloud Storage → Configurations.
2. Configure the bucket and credentials, then Test Connection to verify access.
3. Sync to Bucket uploads your existing files to GCS in one click.
Requirements
- Odoo 19.0 (Community or Enterprise).
- Python package
google-cloud-storageinstalled on the server. - A Google Cloud Storage bucket and a service account with object access on it.
Google Cloud Filestore
Store the Odoo filestore (ir.attachment) in a Google Cloud Storage bucket, with one-click sync and a simple configuration screen.
Features
- Transparent storage of new attachments into a GCS bucket.
- Test Connection button to validate credentials and bucket access.
- Sync to Bucket / Sync to Local to migrate files in either direction.
- Optional delete local copy after upload to free disk space.
- Local-filestore fallback when GCS is unreachable.
- Clean Odoo 19 raw-bytes storage API (no legacy base64).
Requirements
- Odoo 19.0
- google-cloud-storage Python package on the server.
- A GCS bucket and a service-account JSON key with object access on it.
Configuration
- Go to Settings -> Google Cloud Storage -> Configurations.
- Create a configuration: Project ID, Bucket Name, Location and the Service Account JSON file.
- Click Test Connection.
- Enable Active to start storing new attachments in GCS.
- Use Sync to Bucket to upload existing files (or Sync to Local to reverse).
Support
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module