cancel
Showing results for 
Search instead for 
Did you mean: 

How can I configure Nuxeo to store binary files in an SQL database?

Nikkol_John_Mor
Champ in-the-making
Champ in-the-making

Ok, so far I know that Nuxeo, by default, stores its binary files to a path "var/lib/nuxeo/data". My first issue was that every time I rebuild my Nuxeo docker image, the contents of that directory disappears. The first solution I opted to was to mount "var/lib/nuxeo/data" to a docker volume on the machine where my Nuxeo instance resides. This solution solved the issue of "persistence" as I am now able to rebuild my Nuxeo docker image and have my existing binary files accessible after the rebuild.

The problem now is that whenever I try to access the document containing the file on a machine with a different file system, it cannot access the document. But when I access it using the machine with the same file system, I am able to access it. My question is that, is there a solution wherein I can make my binary store persistent after rebuild, at the same time make it available to different machines with different file systems?

The title mentions of a specific solution, but I cannot seem to find a configuration or instructions to do it, so I resort to the community.

10 REPLIES 10

No, I'm just using the standard /var/lib/nuxeo/data filesystem store for the binaries. I didn't bother putting them in the PostgreSQL database. The binaries are archived with tar czf nuxeo_backup.tar.gz -C /var/lib/nuxeo/data/ and unarchived on another system with tar xzpf nuxeo_backup.tar.gz -C /var/lib/nuxeo/data. I put running the load_nuxeo script into our Vagrant provision step.

Getting started

Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.