App Deployments (5): document catalog examples (strfry / route96 / Blossom)#224
Merged
Conversation
Final MVP increment of the App Deployments epic. Ships validated compose definitions for the launch catalog. - lnvps_api_admin::app_seeds: strfry, HAVEN, route96 (+MariaDB, generated secrets + backups), and a generic Blossom server. Each is a validated lnvps_compose document exercising the grammar (ports/ingress, files, volumes, secrets, resources). - seed_launch_apps(db): idempotently inserts any missing apps DISABLED (operator reviews/prices before offering) with the footprint computed from the compose. Wired into generate_demo_data. - Tests: every launch compose parses + has a non-zero footprint; seeding is idempotent (MockDb). Part of work/app-deployments.md (MVP increments 1-5 complete; backups and L4/zap-stream remain as future increments).
Read each project's actual docs and fixed the images/config: - strfry: community dockurr/strfry (no official image); config at /etc/strfry.conf with bind 0.0.0.0; db under /app/strfry-db. - route96: voidic/route96 (not ghcr) + MariaDB reached via service 'db'; config is a YAML file at /app/config.yaml (listen/database/storage_dir/ public_url), matching route96's config.prod.yaml + docker-compose. - blossom: ghcr.io/hzrd149/blossom-server; YAML config at /app/config.yml; publicDomain is a bare hostname; SQLite + blobs under /app/data. Dropped HAVEN: no official image, and the community haven-docker image requires a mounted templates/ directory of binary web assets + 4 JSON files, which the ConfigMap-file model can't provide cleanly. Deferred.
Contributor
Author
|
Corrected the launch composes after actually reading each project's deploy docs:
|
Seeding apps into the DB is the wrong fit — pricing and enabling are operator decisions. Remove the app_seeds module + demo-data wiring and instead provide docs/managed-app-examples.md: ready-to-paste, docs-accurate compose definitions (strfry via dockurr/strfry, route96 + MariaDB via voidic/route96, Blossom via ghcr.io/hzrd149/blossom-server) with how to add them through POST /api/admin/v1/apps, plus notes on HAVEN/zap-stream not being cleanly deployable yet.
v0l
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Final increment of the managed App Deployments epic. Instead of auto-seeding apps into the DB (pricing + enabling are operator decisions), this ships a reference doc with ready-to-paste, docs-accurate
composedefinitions.docs/managed-app-examples.mddockurr/strfry(no official image); config at/etc/strfry.conf(bind = 0.0.0.0); data under/app/strfry-db.voidic/route96; YAML config at/app/config.yaml; DB reached via the in-namespace servicedb; per route96'sconfig.prod.yaml.ghcr.io/hzrd149/blossom-server; YAML config at/app/config.yml; barepublicDomain; SQLite + blobs under/app/data.POST /api/admin/v1/apps+ the compose-grammar recap.templates/dir of binary assets + JSON lists) and zap-stream (needsexpose: tcp/udp) aren't cleanly deployable yet.Removes the earlier
app_seedsmodule + demo-data wiring.