patternMinor
Are there any truly simple artifact repositories?
Viewed 0 times
simpleartifactareanytrulyrepositoriesthere
Problem
I'm looking for a binary-artifact repository, but everything I see is super complicated, to set up, use, and manage. All I'm looking for is:
Even a web-based portal is almost more than what I need (sure, it would be nice.)
Doesn't seem like it should require all the infrastructure and complexity of archiva, artifactory, etc. Or maybe some of these tools have a simple mode and I just can't find it?
- upload repos as tgz/zip with metadata (name, date, tag)
- query and download by SHA and/or name
- a local tool (python-based?) to help create repos from a subdir with the proper metadata and signature
Even a web-based portal is almost more than what I need (sure, it would be nice.)
Doesn't seem like it should require all the infrastructure and complexity of archiva, artifactory, etc. Or maybe some of these tools have a simple mode and I just can't find it?
Solution
I didn't find anything that was exactly what I was looking for; simple zip/tar and even dpkg didn't have the traceability I was hoping for in a binary-artifact system, so I wrote my own: see https://github.com/garyo/binary-artifact (MIT licensed).
It's basically a glorified tar/zip creator that creates a manifest with a content signature and a well-defined file name that includes the content sig, so the artifact can be specified in a build file (e.g. Ansible/Puppet/Chef/SCons) in a repeatable, traceable way.
This way the artifacts can live anywhere the build system can find them (Google drive, Dropbox, local NAS, whatever), download them knowing exactly which version is being downloaded (thanks to the specific name), and unpack and use them as usual. This tool makes no assumptions about where the artifacts get stored.
It's basically a glorified tar/zip creator that creates a manifest with a content signature and a well-defined file name that includes the content sig, so the artifact can be specified in a build file (e.g. Ansible/Puppet/Chef/SCons) in a repeatable, traceable way.
This way the artifacts can live anywhere the build system can find them (Google drive, Dropbox, local NAS, whatever), download them knowing exactly which version is being downloaded (thanks to the specific name), and unpack and use them as usual. This tool makes no assumptions about where the artifacts get stored.
Context
StackExchange DevOps Q#5051, answer score: 1
Revisions (0)
No revisions yet.