Files
recap/startos-registry/scripts/publish.sh
T
Keysat 9282440143 Rename project: youtube-summarizer → recap
The product was always more than YouTube — it handles podcast feeds
too, and the upcoming multi-provider work makes it less Gemini-
specific. New name: Recap.

This is a coordinated identity change across:

  • StartOS package id: youtube-summarizer → recap
    (manifest.id; the .s9pk filename, Docker image namespace, and
    install path under StartOS all derive from this automatically)
  • Display name: "YouTube Summarizer" → "Recap"
    (manifest title, activation screen heading, page <title>, console
    log on boot, i18n strings, ABOUT.md, Dockerfile header,
    docker_entrypoint banner)
  • Keysat product slug: youtube-summarizer → recap
    (server/license.js PRODUCT_SLUG; frontend fallback strings)
  • Daemon subscription id: youtube-summarizer-sub → recap-sub
  • Env var prefix: YT_SUMMARIZER_* → RECAP_*
    (LICENSE_KEY, LICENSE_KEY_PATH, MAX_OFFLINE_DAYS,
    VALIDATE_INTERVAL_MS)
  • localStorage keys: yt-summarizer-* → recap-*
    (gemini-key, activation-skipped, clips)
  • Library export filename: youtube-summarizer-library.json →
    recap-library.json
  • npm package names: youtube-summarizer-{startos,server} → recap-*
  • Deploy paths: youtube-summarizer_x86_64.s9pk → recap_x86_64.s9pk
    (default values in bin/deploy.sh; .deploy.env on dev machine
    needs the same update before next push)
  • Self-hosted registry directory: startos-registry/packages/
    youtube-summarizer → .../recap (with package.json + INSTRUCTIONS
    rewritten)

What does NOT change:
  • Filesystem repo path (still /Users/.../youtube-summarizer/)
  • Git history / commit messages
  • Existing version files in startos/versions/ (kept as-is — the
    version chain belongs to the package's own history regardless of
    its display name)

User-side follow-ups required:
  1. Create "recap" product in Keysat admin, set up Core/Pro tier
     policies (same entitlements as before), mint a fresh test
     license. Old "youtube-summarizer" licenses won't activate
     against the new slug.
  2. Update .deploy.env (gitignored) so FILEBROWSER_PATH and
     REGISTRY_PUBLIC_URL point at recap_x86_64.s9pk.

StartOS will treat this as a brand-new app on install — existing
youtube-summarizer installs will not auto-migrate (acknowledged
intentional given no real users yet).
2026-05-08 13:35:27 -05:00

68 lines
2.2 KiB
Bash
Executable File

#!/bin/bash
# ============================================================================
# publish.sh - Upload a new package version to your registry
# ============================================================================
# Run this from your LOCAL machine (where you build .s9pk files).
#
# Usage:
# ./scripts/publish.sh <package-id> <s9pk-file> [vps-host]
#
# Examples:
# ./scripts/publish.sh recap ./recap_x86_64.s9pk
# ./scripts/publish.sh recap ./recap_x86_64.s9pk root@123.45.67.89
#
# What it does:
# 1. Uploads the .s9pk file to the VPS
# 2. Signals the registry to reload its config
#
# IMPORTANT: Before running this, update the version in
# packages/<id>/package.json on the VPS (or locally then scp).
# ============================================================================
set -euo pipefail
PKG_ID="${1:?Usage: publish.sh <package-id> <s9pk-file> [vps-host]}"
S9PK_FILE="${2:?Usage: publish.sh <package-id> <s9pk-file> [vps-host]}"
VPS_HOST="${3:-root@5.161.191.254}"
REMOTE_DIR="/opt/startos-registry/packages/$PKG_ID"
if [ ! -f "$S9PK_FILE" ]; then
echo "Error: File not found: $S9PK_FILE"
exit 1
fi
S9PK_BASENAME="$(basename "$S9PK_FILE")"
S9PK_SIZE="$(du -h "$S9PK_FILE" | cut -f1)"
echo ""
echo " Publishing to StartOS Registry"
echo " ==============================="
echo " Package: $PKG_ID"
echo " File: $S9PK_BASENAME ($S9PK_SIZE)"
echo " Target: $VPS_HOST:$REMOTE_DIR"
echo ""
# Upload the .s9pk
echo "[1/3] Uploading $S9PK_BASENAME..."
scp "$S9PK_FILE" "$VPS_HOST:$REMOTE_DIR/$S9PK_BASENAME"
# Copy updated package.json if it exists locally
LOCAL_PKG_JSON="./packages/$PKG_ID/package.json"
if [ -f "$LOCAL_PKG_JSON" ]; then
echo "[2/3] Uploading updated package.json..."
scp "$LOCAL_PKG_JSON" "$VPS_HOST:$REMOTE_DIR/package.json"
else
echo "[2/3] No local package.json found, skipping config upload."
echo " Make sure to update the version in $REMOTE_DIR/package.json on the VPS!"
fi
# Reload the registry (SIGHUP triggers config reload without downtime)
echo "[3/3] Reloading registry..."
ssh "$VPS_HOST" "systemctl reload startos-registry"
echo ""
echo " Done! Package $PKG_ID published."
echo " Verify: https://registry.satsflows.com/package/v0/version/$PKG_ID"
echo ""