⚠️ Warning: This project is still under heavy development, to be considered a beta, at best.

Backpack is used to collect and store a varied and large amounts of artifacts, for example npm, nuget...

Primary use-case is transferring to airgapped / high security networks for offline consumption via an artifact repository.

The complex keeps track of already collected artifacts, dependencies, and versions.

The Backpack's collection of artifacts is greedy, it will by default collect every version and every dependency version, recursively, until every item is collected, artifact filters can be applied to reduce the amount collected.

It builds daily deltas to reduce the day-to-day load on the transfer device.

The design is microservice oriented and intended to minimize the amount of work needed to build a new "Processor", for example maven.

Processors can safely rely on the core infrastructure of Backpack, the core infrastructure handles the memorization of metadata, and the collection via standard protocols, for example http, git, or docker.

An early stage helm chart is available at https://github.com/linus-berg/helm-charts/tree/main/charts/backpack

https://linus-berg.github.io/helm-charts/

See the values.examples.yaml file for configuration. The auxiliary services such as mongodb still needs to be provided by the administrator.

Backpack is designed to be horizontally scalable and suitable for kubernetes, however, kubernetes deployments have not been tested thoroughly.

The following services are required to run the complete suite of Backpack capabilities. A batteries included starter pack is included under /examples and /Compose, however, these are not production ready configurations, and are only intended as an development/test environment.