Federated cpak Store System

cpak is decentralized by design: you can install any package by its Git origin:

cpak install github.com/containerpak/chrome

Optionally, you can register federated indexes ("stores") to search and manage multiple collections of packages.

Overview

A federated store is a Git repository containing a collection of categories, each with a set of packages. Each package is defined by a manifest.json file that describes the package's metadata.

Submitting Apps to a Store

1. Fork or open a PR against the store repo.
2. Add your manifest.json under the correct category:

   Music/github/com/yourorg/yourapp/manifest.json
   

   as you can see, the path is a combination of the category and the Git origin of the package, following a Go-style package path convention.
3. On each PR commit, the CI bot automatically:
   • Validates the manifest schema
   • Attempts cpak install <origin> against the PR index.

Then moderators will review the PR and occasionally request changes. Then the following steps will be taken:

1. A moderator run !publish in the PR to trigger the CI bot.
2. CI regenerates both index.json and timestamp.json in the same branch as the PR.
3. After a successful publish, maintainers merge the PR into the main branch, making the new package available to all users.

Managing Federated Stores

cpak store-add <uri>

Registers a new remote store.

cpak store-add github.com/containerpak/store

cpak store-list

Lists all configured remote stores:

cpak store-list

- github.com/containerpak/store        
- github.com/anotherorg/another-store/ 

cpak store-remove <uri>

Removes a store by its URI:

cpak store-remove github.com/containerpak/store

Searching & Installing Packages

cpak install spotify

1. github.com/spotifyltd/spotify
2. github.com/spotifier/spotify-ultra

Which cpak do you want to install? (1-2): 1

Repository Structure

Each store repo should use this layout:

root/
├── categories/
├──── Music/
│     ├── github/com/org1/app1/manifest.json
│     │   ├── github/com/org2/app2/manifest.json
│     ├── index.json
│     └── ...
├── index.json
└── timestamp.json

• manifest.json files must match the manifest schema.
• index.json and timestamp.json are generated; do not edit.