@spacemade/ui 0.0.1

package/cmd.sh

@@ -0,0 +1,152 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+ROOT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+ENV_FILE="${ENV_FILE:-${ROOT_DIR}/.env}"
+
+args=("$@")
+
+load_env() {
+  if [[ -f "$ENV_FILE" ]]; then
+    while IFS='=' read -r key value; do
+      [[ -z "${key:-}" ]] && continue
+      [[ "$key" =~ ^# ]] && continue
+
+      key="$(echo -e "${key}" | tr -d '[:space:]')"
+      value="$(echo -e "${value:-}" | sed -e 's/^[[:space:]]*//' -e 's/[[:space:]]*$//')"
+
+      [[ -z "$key" ]] && continue
+      [[ "$key" =~ [^A-Za-z0-9_]+ ]] && continue
+
+      export "$key"="$value"
+    done < "$ENV_FILE"
+  fi
+}
+load_env
+
+usage() {
+  cat <<'EOFUSAGE'
+Usage: ./cmd.sh <command> [args]
+
+General:
+  init cms [--force]         Generate the default CMS install system scaffold
+  init simple-cms [--force]  Generate the simple CMS scaffold
+  init gallery [--force]     Generate the image gallery scaffold
+  init nft [--force]         Generate the NFT marketplace scaffold
+  init gpu [--force]         Generate the GPU marketplace scaffold
+  init metaverse [--force]   Generate the metaverse hosting scaffold
+  init all [--force]         Run all product scaffolds
+  migrate <product>          Run product migrations from api/lib/<product>/migrations
+  help                   Show this help output
+EOFUSAGE
+}
+
+run_generator() {
+  local script_name="${1:-}"
+  local extra_arg="${2:-}"
+  cd "$ROOT_DIR"
+
+  if [[ "$extra_arg" == "--force" ]]; then
+    npm run "$script_name" -- --force
+  else
+    npm run "$script_name"
+  fi
+}
+
+init() {
+  local mode="${1:-cms}"
+  local extra_arg="${2:-}"
+
+  case "$mode" in
+    cms)
+      run_generator "generate:cms" "$extra_arg"
+      ;;
+    simple-cms)
+      run_generator "generate:simple-cms" "$extra_arg"
+      ;;
+    gallery)
+      run_generator "generate:gallery" "$extra_arg"
+      ;;
+    nft)
+      run_generator "generate:nft" "$extra_arg"
+      ;;
+    gpu)
+      run_generator "generate:gpu" "$extra_arg"
+      ;;
+    metaverse)
+      run_generator "generate:metaverse" "$extra_arg"
+      ;;
+    all)
+      run_generator "generate:cms" "$extra_arg"
+      run_generator "generate:simple-cms" "$extra_arg"
+      run_generator "generate:gallery" "$extra_arg"
+      run_generator "generate:nft" "$extra_arg"
+      run_generator "generate:gpu" "$extra_arg"
+      run_generator "generate:metaverse" "$extra_arg"
+      ;;
+    *)
+      echo "Unknown init mode: $mode" >&2
+      echo "Use one of: cms, simple-cms, gallery, nft, gpu, metaverse, all" >&2
+      exit 1
+      ;;
+  esac
+}
+
+docker_compose_available() {
+  command -v docker-compose >/dev/null 2>&1
+}
+
+docker_api_is_running() {
+  docker_compose_available && docker-compose ps -q api >/dev/null 2>&1 && [[ -n "$(docker-compose ps -q api)" ]]
+}
+
+migrate() {
+  local product="${1:-}"
+
+  if [[ -z "$product" ]]; then
+    echo "Missing product name. Example: ./cmd.sh migrate simple-cms" >&2
+    exit 1
+  fi
+
+  if [[ ! "$product" =~ ^[a-z0-9][a-z0-9-]*$ ]]; then
+    echo "Invalid product name: $product" >&2
+    exit 1
+  fi
+
+  local migration_path="lib/${product}/migrations"
+  local migration_dir="${ROOT_DIR}/api/${migration_path}"
+
+  if [[ ! -d "$migration_dir" ]]; then
+    echo "No migrations found at api/${migration_path}" >&2
+    exit 1
+  fi
+
+  cd "$ROOT_DIR"
+
+  if docker_api_is_running; then
+    docker-compose exec -T api npx sequelize db:migrate --migrations-path "$migration_path"
+    return
+  fi
+
+  cd "${ROOT_DIR}/api"
+  npx sequelize db:migrate --migrations-path "$migration_path"
+}
+
+main() {
+  local cmd="${1:-}"
+  shift || true
+  load_env
+
+  case "$cmd" in
+    init) init "$@" ;;
+    migrate) migrate "$@" ;;
+    help|-h|--help|"") usage ;;
+    *)
+      echo "Unknown command: $cmd" >&2
+      usage
+      exit 1
+      ;;
+  esac
+}
+
+main "$@"

package/docs/cms-quickstart.md

@@ -0,0 +1,206 @@
+# CMS Quickstart
+
+This guide is for using `appstudio` as the base repo for a CMS-focused admin product.
+
+The main `README.md` stays generic on purpose. This file is the product-specific quickstart for a CMS-style control plane.
+
+## Goal
+
+Build an Admin app that can:
+
+- sell plans
+- launch subscribed products as deployments
+- connect deployments to core sites
+- handle backups
+- support operations teams
+
+## Recommended Domain Models
+
+Start with these product models on top of the App Studio core:
+
+- `DeploymentTemplate`
+- `Deployment`
+- `DeploymentJob`
+- `DeploymentBackup`
+
+## Suggested Responsibilities
+
+### `Deployment`
+
+Use for the primary customer-owned launch record for a subscribed product.
+
+Suggested fields:
+
+- `id`
+- `orgId`
+- `projectId`
+- `siteId`
+- `productId`
+- `productPlanId`
+- `subscriptionId`
+- `providerId`
+- `deploymentSpecKey`
+- `deploymentValues`
+- `name`
+- `slug`
+- `status`
+- `templateId`
+- `runtimeKey`
+- `ownerUserId`
+- `createdAt`
+- `updatedAt`
+
+### Product Deployment Metadata
+
+Use the core product layer to store reusable deployment metadata. This follows the older cloud app pattern where catalog/product versions hold `resourceUrl`, `resourceSpec`, and `resourceParams`, while deployments hold only runtime selection and values.
+
+Until `ProductVersion` exists in App Studio, store provider-specific deployment options in `Product.formSpecs`.
+
+For example:
+
+- CMS on AWS can save a deployment option with `providerKey: aws`, `specFormat: cloudformation`, and a `resourceUrl` pointing at the CloudFormation template.
+- CMS on Google can save a deployment option with `providerKey: google`, `specFormat: terraform`, and Terraform source/module metadata.
+- CMS on Azure can save a deployment option with `providerKey: azure`, `specFormat: terraform`, `script`, or a future Azure-native format.
+
+Example `formSpecs` value:
+
+```json
+[
+  {
+    "key": "aws-cloudformation",
+    "label": "AWS CloudFormation",
+    "providerKey": "aws",
+    "specFormat": "cloudformation",
+    "resourceUrl": "s3://templates/cms/cloudformation.yaml"
+  },
+  {
+    "key": "google-terraform",
+    "label": "Google Terraform",
+    "providerKey": "google",
+    "specFormat": "terraform",
+    "resourceUrl": "git::https://example.com/cms/terraform/google.git"
+  }
+]
+```
+
+Deployments should not pass template/buildspec blobs through URLs or launch requests. The launch request should pass IDs plus the selected `deploymentSpecKey` and runtime `deploymentValues`.
+
+### `DeploymentTemplate`
+
+Use for deployment blueprints or starter site definitions.
+
+Suggested fields:
+
+- `id`
+- `name`
+- `slug`
+- `description`
+- `version`
+- `isActive`
+
+### `DeploymentJob`
+
+Use for async deployment creation and operational jobs.
+
+Suggested fields:
+
+- `id`
+- `deploymentId`
+- `productId`
+- `subscriptionId`
+- `providerId`
+- `deploymentSpecKey`
+- `jobType`
+- `status`
+- `payload`
+- `startedAt`
+- `finishedAt`
+- `errorMessage`
+
+### `DeploymentBackup`
+
+Use for backup and restore tracking.
+
+Suggested fields:
+
+- `id`
+- `deploymentId`
+- `backupType`
+- `storageKey`
+- `status`
+- `createdAt`
+
+## Recommended API Areas
+
+Create API routes such as:
+
+- `api/pages/api/cms-templates/index.ts`
+- `api/pages/api/cms-deployments/index.ts`
+- `api/pages/api/cms-deployments/launchable-products.ts`
+- `api/pages/api/cms-deployment-jobs/index.ts`
+- `api/pages/api/cms-backups/index.ts`
+
+## Generator
+
+App Studio includes a generator script for the default CMS install system scaffold.
+
+Run:
+
+```bash
+npm run generate:cms
+```
+
+This creates starter files for:
+
+- API models
+- services
+- controllers
+- API route handlers
+- frontend store placeholders
+- starter product pages
+
+Use overwrite mode when you intentionally want to regenerate:
+
+```bash
+npm run generate:cms -- --force
+```
+
+## Recommended UI Areas
+
+The app picker should show `Deployments` as the top-level app entry, matching the `/storage` pattern. The related CMS routes remain available inside the generated deployments area:
+
+- `/templates`
+- `/deployments`
+- `/deployment-jobs`
+- `/backups`
+
+Deployment detail pages should expose quick actions for Templates, Deployment Jobs, and Backups. Those actions can be wired to deployment-scoped views later.
+
+## Deployment Flow
+
+Typical lifecycle:
+
+1. Customer signs up.
+2. Customer creates an org.
+3. Customer picks a product or plan.
+4. Billing creates an active subscription.
+5. The deployment UI calls `/cms-deployments/launchable-products` to list subscribed product plans that do not yet have a `Deployment`.
+6. Customer selects one subscribed product and one provider/deployment option, such as AWS/CloudFormation or Google/Terraform.
+7. System creates a `Deployment` with `productId`, `productPlanId`, `subscriptionId`, `providerId`, `deploymentSpecKey`, and `deploymentValues`, then queues a `DeploymentJob`.
+8. Provisioning marks the deployment ready and links it to a core `Site`.
+9. Customer manages domains through the site layer and manages backups/settings through the deployment layer.
+
+## Billing Mapping
+
+Map Stripe entitlements to CMS-specific limits such as:
+
+- `deployment_limit`
+- `cms_template_limit`
+- `backup_retention_days`
+
+## Recommendation
+
+Keep this as a product-layer guide.
+
+- `README.md` stays generic for all Admin products
+- `docs/cms-quickstart.md` stays specific for CMS products

package/docs/gallery-quickstart.md

@@ -0,0 +1,24 @@
+# Gallery Quickstart
+
+Use this when you want an art gallery product where users type prompts, generate images, and organize those images into galleries.
+
+Suggested models:
+
+- `Gallery`
+- `GalleryImage`
+- `ImageGeneration`
+- `PromptTemplate`
+- `GalleryShareLink`
+
+Suggested workflows:
+
+- prompt for image generation
+- review outputs
+- move images into galleries
+- share galleries publicly
+
+Generate the scaffold with:
+
+```bash
+./cmd.sh init gallery
+```

package/docs/gpu-marketplace-quickstart.md

@@ -0,0 +1,27 @@
+# GPU Marketplace Quickstart
+
+Use this when you want to build a marketplace where home GPU owners list devices online and renters consume them as provider-backed capacity.
+
+Suggested models:
+
+- `GpuHost`
+- `GpuDevice`
+- `GpuListing`
+- `GpuBooking`
+- `GpuProviderAdapter`
+
+Suggested workflows:
+
+- onboard GPU hosts
+- register GPU devices
+- publish listings with hourly pricing
+- create renter bookings
+- expose listings as provider inventory for the parent Osirus app
+
+Generate the scaffold with:
+
+```bash
+./cmd.sh init gpu
+```
+
+Use domains and proxy routing later to direct renters or provider traffic into the correct host endpoints.

package/docs/metaverse-quickstart.md

@@ -0,0 +1,25 @@
+# Metaverse Quickstart
+
+Use this when you want to build a company that hosts and manages virtual worlds and their item inventories.
+
+Suggested models:
+
+- `World`
+- `WorldItem`
+- `WorldInstance`
+- `WorldDomain`
+- `WorldDeployJob`
+
+Suggested workflows:
+
+- create hosted worlds
+- deploy and update worlds
+- attach domains to worlds
+- manage world items and assets
+- track hosting lifecycle by world
+
+Generate the scaffold with:
+
+```bash
+./cmd.sh init metaverse
+```

package/docs/migration-plan.md

@@ -0,0 +1,41 @@
+# Migration Plan
+
+## Goal
+
+Build `appstudio` as the reusable starter while keeping `osirus-ai` free to continue as a product implementation.
+
+## Sequence
+
+1. Extract shared configuration:
+   - app identity
+   - navigation
+   - enabled modules
+   - billing defaults
+2. Extract core backend domains:
+   - auth
+   - user
+   - org
+   - project
+   - provider
+   - product
+   - subscription
+   - invoice
+3. Extract core frontend surfaces:
+   - auth pages
+   - account/settings
+   - admin shell
+   - projects
+   - providers
+   - billing
+4. Gate AI features behind module registration.
+5. Port AI features one module at a time when needed.
+
+## First Success Criteria
+
+The first successful bootstrap should:
+
+- sign in and sign up users
+- manage orgs and projects
+- manage providers
+- show pricing and checkout flows
+- run without chat, search, images, video, or speech enabled

package/docs/modules.md

@@ -0,0 +1,34 @@
+# App Studio Modules
+
+## Core Modules
+
+These should exist in every generated application:
+
+- `auth`
+- `users`
+- `orgs`
+- `projects`
+- `providers`
+- `billing`
+- `media`
+- `admin`
+
+## Optional Modules
+
+These should be installable only when a product needs them:
+
+- `ai-chat`
+- `ai-search`
+- `ai-images`
+- `ai-video`
+- `ai-speech`
+- `ai-agents`
+- `vector-store`
+- `cms`
+
+## Module Rules
+
+- Core modules must not depend on optional AI modules.
+- Optional modules may depend on core modules.
+- Product branding and homepage content belong outside modules.
+- Seed data should be split into core data and product-specific data.

package/docs/nft-quickstart.md

@@ -0,0 +1,26 @@
+# NFT Quickstart
+
+Use this when you want an NFT gallery or marketplace product with collections, minted items, and listings.
+
+Suggested models:
+
+- `NftCollection`
+- `NftItem`
+- `MintJob`
+- `WalletAccount`
+- `MarketplaceListing`
+- `RoyaltyProfile`
+
+Suggested workflows:
+
+- create collections
+- add token items
+- mint to blockchain
+- connect wallets
+- list items for sale
+
+Generate the scaffold with:
+
+```bash
+./cmd.sh init nft
+```

package/docs/simple-cms-quickstart.md

@@ -0,0 +1,22 @@
+# Simple CMS Quickstart
+
+Use this when you want lightweight file publishing on top of the core `Site` system instead of a full deployment product.
+
+Suggested models:
+
+- `Site` from the core app
+- `AppFile`
+- `AppFileRevision`
+
+Suggested workflows:
+
+- create sites with the core site tools
+- create app files under sites
+- publish and unpublish files
+- manage domains through the site layer
+
+Generate the scaffold with:
+
+```bash
+./cmd.sh init simple-cms
+```

package/middleware.ts

@@ -0,0 +1,77 @@
+import type { NextRequest } from 'next/server'
+import { NextResponse } from 'next/server'
+
+import { readSessionFromRequest, isAuthenticatedSession } from './src/lib/auth'
+import { getAppBasePath, isInsideAppBasePath, stripAppBasePath } from './src/lib/app-paths'
+import { canAccessRouteModule } from './src/lib/security'
+import { isRouteAllowed } from './src/lib/routes'
+import type { ModuleKey } from './src/config/modules'
+
+const publicRoutes = new Set(['/', '/pricing'])
+
+const routeToModule: Array<{ prefix: string; key: ModuleKey }> = [
+  { prefix: '/activity', key: 'activity' },
+  { prefix: '/addresses', key: 'addresses' },
+  { prefix: '/forms', key: 'forms' },
+  { prefix: '/invoices', key: 'invoices' },
+  { prefix: '/media', key: 'media' },
+  { prefix: '/orgs', key: 'orgs' },
+  { prefix: '/posts', key: 'posts' },
+  { prefix: '/products', key: 'products' },
+  { prefix: '/projects', key: 'projects' },
+  { prefix: '/providers', key: 'providers' },
+  { prefix: '/purchases', key: 'purchases' },
+  { prefix: '/settings', key: 'settings' },
+  { prefix: '/sites', key: 'sites' },
+  { prefix: '/subscriptions', key: 'subscriptions' },
+  { prefix: '/tags', key: 'tags' },
+  { prefix: '/tickets', key: 'tickets' },
+  { prefix: '/usage', key: 'usage' },
+  { prefix: '/users', key: 'users' },
+  { prefix: '/admin', key: 'admin' },
+]
+
+export function middleware(request: NextRequest) {
+  const { pathname } = request.nextUrl
+  const appBasePath = getAppBasePath()
+
+  if (
+    pathname.startsWith('/_next') ||
+    pathname.startsWith('/api') ||
+    pathname === '/favicon.ico'
+  ) {
+    return NextResponse.next()
+  }
+
+  if (appBasePath && pathname === '/') {
+    return NextResponse.redirect(new URL(appBasePath, request.url))
+  }
+
+  if (!isInsideAppBasePath(pathname)) {
+    return NextResponse.next()
+  }
+
+  const appPathname = stripAppBasePath(pathname)
+  const session = readSessionFromRequest(request)
+  const matchedRoute = routeToModule.find(
+    (item) => appPathname === item.prefix || appPathname.startsWith(`${item.prefix}/`)
+  )
+
+  if (matchedRoute && !isAuthenticatedSession(session) && !publicRoutes.has(appPathname)) {
+    return NextResponse.redirect(new URL('/?auth=required', request.url))
+  }
+
+  if (isRouteAllowed(appPathname)) {
+    if (matchedRoute && !canAccessRouteModule(session, matchedRoute.key)) {
+      return NextResponse.redirect(new URL('/?denied=1', request.url))
+    }
+
+    return NextResponse.next()
+  }
+
+  return NextResponse.redirect(new URL('/', request.url))
+}
+
+export const config = {
+  matcher: ['/((?!.*\\..*).*)'],
+}

package/next-env.d.ts

@@ -0,0 +1,6 @@
+/// <reference types="next" />
+/// <reference types="next/image-types/global" />
+import "./.next/dev/types/routes.d.ts";
+
+// NOTE: This file should not be edited
+// see https://nextjs.org/docs/app/api-reference/config/typescript for more information.

package/next.config.ts

@@ -0,0 +1,39 @@
+import type { NextConfig } from 'next'
+import path from 'path'
+
+const apiOrigin = (() => {
+  const envApiUrl =
+    process.env.NEXT_PUBLIC_API_URL ||
+    process.env.NEXT_PUBLIC_API_HOST
+
+  if (envApiUrl) {
+    return envApiUrl.replace(/\/+$/, '')
+  }
+
+  const apiHost = process.env.API_HOST || 'api'
+  const apiPort = process.env.API_PORT || '3001'
+  return `http://${apiHost}:${apiPort}`
+})()
+
+const nextConfig: NextConfig = {
+  reactStrictMode: true,
+  transpilePackages: ['@spacemade/ui', '@spacemade/api'],
+  async rewrites() {
+    return [
+      {
+        source: '/api/:path*',
+        destination: `${apiOrigin}/api/:path*`,
+      },
+    ]
+  },
+  env: {
+    NEXT_PUBLIC_APP_ENV: process.env.APP_ENV,
+  },
+  sassOptions: {
+    includePaths: [path.join(process.cwd(), 'src', 'sass')],
+    quietDeps: true,
+    silenceDeprecations: ['import', 'global-builtin', 'color-functions'],
+  },
+}
+
+export default nextConfig