The Logos Eco Dev sample-apps catalog — one repository URL that installs the sample apps built and actively maintained by the Logos Ecosystem Development team.

https://raw.githubusercontent.com/logos-co/logos-ecodev-catalog/main/logos-repo.json

Paste it into Logos Basecamp → Settings → Repositories → Add repository, then install from the App Manager.

Built from logos-co/logos-modules-release-base (see logos-co/ecosystem#157): this repo holds the submodules and catalog metadata; all release machinery lives in the versioned, reusable logos-co/logos-modules-release-action. Per that issue's direction, the app list is the aggregate of the team's individual catalogs, keeping only apps that are actively maintained.

What's in the catalog

App	What it does	Maintainer	Source
Keycard	Keycard smartcard authentication	Alisher	`xAlisher/keycard-basecamp`
Soulseek	Soulseek music search & playlists (core + UI)	Alisher / Dario	`xAlisher/soulseek-basecamp`, `xAlisher/soulseek-ui`
Booth	Anonymous sovereign radio over Tor (core + UI)	Alisher	`xAlisher/booth-basecamp`
Hello	Minimal universal module + QML UI; proves the release path	Dario	`dlipicar/logos-hello-module`, `dlipicar/logos-hello-ui`
LEZ Faucet	Request a 150 LEZ testnet drop (core + UI)	Danish	`logos-co/lez-faucet`
Atomic Swaps	ETH ↔ LEZ atomic swaps on the LEZ testnet (core + UI)	Danish	`logos-co/eth-lez-atomic-swaps`

Faucet, Swaps, and Booth are multi-module repos (their metadata.json files live one directory down); releasing them from a catalog needs logos-modules-release-action#16 — until it lands their release workflows fail at checkout. Everything else releases today.

Not included

Deliberately lean for now — Alisher's other basecamp apps (stash, beacon, keeper, cord, ia, receiver, snake) were trimmed to his top three; add any back with add-module.sh when wanted.
Node Remote (xAlisher/node-remote) — no buildable module at its root or one level down; it's a multi-component repo (node-remote-bc/, node-remote-android/).
docs-logos, logos-blockchain-module/-ui, logos-zone-sequencer-module — present in individual catalogs but they are infra forks / docs, not eco dev sample apps.

Adding your app (team members)

git clone https://github.com/logos-co/logos-ecodev-catalog
cd logos-ecodev-catalog
./scripts/add-module.sh https://github.com/<you>/<your-app-repo>   # [name] [branch] optional
git add -A && git commit -m "Add <your-app-repo>" && git push

add-module.sh registers the submodule and generates one release workflow per module it finds — a metadata.json (name + version, plus a buildable Nix flake) at the repo root, or one per subdirectory for a multi-module repo.

Removing an app is the reverse: git rm submodules/<name>, delete .github/workflows/release-<name>.yml, then run Unpublish from the Actions tab (with dry_run: true first) to drop its releases from the index.

Publishing

From the Actions tab run Release all modules (or an individual Release <module>) — or, from a terminal, ./scripts/catalog.sh release-all. The action builds each .lgx, verifies it, cuts a <module>-v<version> GitHub release, and rolls everything up into the rolling index release that clients read (releases/download/index/index.json — the indexUrl in logos-repo.json).

A new version ships when you bump the submodule pointer (which moves its metadata.json#version) and re-run its workflow; re-running an unchanged submodule is a fast no-op. Both release workflows take a Force build toggle to rebuild and replace an already-published version.

Layout

.
├── logos-repo.json                       # catalog metadata clients read
├── .gitmodules                           # submodule declarations
├── submodules/                           # one git submodule per module
├── scripts/
│   ├── add-module.sh                     # add a submodule + generate its workflow
│   └── catalog.sh                        # run the catalog workflows via `gh` (no Actions tab)
└── .github/workflows/
    ├── _release-module.yml               # signing config — the ONE place to edit it
    ├── release-module.yml.template       # per-module workflow template (don't run; it's a template)
    ├── release-<module>.yml              # one per app, generated by add-module.sh
    ├── release-all.yml                   # umbrella; discovers modules from .gitmodules
    ├── rebuild-index.yml                 # rebuilds index.json after each release
    └── unpublish.yml                     # manually remove a module / version from the catalog

Workflow architecture

Two-tier reusable workflows so the signing pipeline lives in exactly one place:

_release-module.yml — local private reusable workflow (workflow_call only). Calls logos-co/logos-modules-release-action/.github/workflows/release.yml@v1 with this catalog's signing configuration.
release-<module>.yml — one per module, generated by add-module.sh. Each just passes module_path: submodules/<repo>[/<module-dir>] to _release-module.yml.
release-all.yml — umbrella. Discovers the module list from the per-module workflows (plus any submodule with no workflow, at its root) at run time and fans out per module in parallel.
rebuild-index.yml — thin passthrough to the action's index-rebuilder. Auto-triggered after each release; also runs on a 6-hourly catch-up schedule.
unpublish.yml — manual (Actions tab). Removes a whole module or one specific version, then rebuilds the index. Run with dry_run: true first — deletion is irreversible.

To change signing for the whole catalog, edit _release-module.yml only — the per-module callers and the umbrella never need touching.

Signing

Publishes unsigned for now (signing_mode: none, matching the empty trustedSigners in logos-repo.json). To turn on signing, follow the inline instructions at the top of .github/workflows/_release-module.yml:

Mode	What runs	Where the key lives
`none` (current)	nothing	n/a — unsigned releases
`inline`	`lgx sign` in CI	`LOGOS_SIGNING_KEY` Actions secret (Ed25519 JWK)
`external`	your `signing_command`	anywhere (Jenkins / HSM / hardware token)

For inline, also put the matching public DID under trustedSigners in logos-repo.json so clients trust the signature.

Notes for cloning

.gitmodules is committed but submodule working trees are not — after cloning, run:

git submodule update --init --recursive