nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Is Nuxeo the right choice for a repository of software binaries?

chris_here_

Hi there,

I'm brand new to Nuxeo, currently evaluating it to create and maintain a local repository of all the third-party software components that are necessary to deploy our own software solution. This means some large binaries like RedHat 6.3, Oracle 11g, TimesTen IMDB, as well a number of smaller ones, including several RPM packages, etc. The goal would be to keep a local copy of those binaries and ISO images and of their updates, with annotations, dependencies and version history.

I have a few questions in this respect:

Is Nuxeo DM a good solution for this kind of usage? Or maybe DAM is better suited? Do others use it Nuxeo for a similar purpose?
Will I be able to work directly on the local copies of the files on the server, without having to go through the GUI? For instance it would be helpful to be able to use symbolic links to the large files directly on the server, when building up a distribution ISO file for instance. I've seen that there's a bulk upload module for v5.6 that allows to load directly from the local filesystems.
Most of those files have their own versioning scheme, for instance for Oracle, 11.2.0.3. Will I be able to label the versions kept by Nuxeo with whatever is used by the 3rd party vendor?
Any other tip or advice?

Thanks to all for your insight,

Chris

Find more posts tagged with

Comments

Benjamin_Jalon1

Nuxeo platform in general suit well for your need. Choosing between DM or DAM will depend of the web interface you want to expose to your users.
yes you can look into the Nuxeo Marketplace the nuxeo-platform-importer package addon
I suggest here to consider the version of third part packages as metadata and Nuxeo version more as version of the Nuxeo document representing the package. So no problem if you do so.
no 🙂

Hope this helps.

Laurent_Doguin

And some customers are already managing software build http://www.nuxeo.com/en/customers/electronic-arts

bruce_Grant

DAM is better suited for visual digital assets - not sure there would be any real value in using the DAM UI for executables and images. In my opinion, DM is a better candidate for what you're planning.
Do you mean working with local server copies of ISOs once they are imported into Nuxeo? Or do you mean importing assets directly from the server?
Even if you didn't want to add custom metadata you could always use the dublincore description field to capture the version number. But, as suggested above a custom version level field makes the most sense.
Given the size of artifacts you will be dealing with, ingestion into Nuxeo via a server-based bulk importer is going to be a requirement. Trying to push GB+ sized files through a client browser just isn't practical. This means you will have to leverage the importer package. Not sure if you know but Nuxeo stores all binaries outside the database and metadata and indices in the database, so the solution is very scalable. As a proof of concept I suggest trying the importer with some of your bigger packages to see how it performs. If performance is a concern there are many tuning opportunities at all levels of the software and hardware stacks!