Local Development

Run the full SirSluginston stack locally with JSON files. No cloud account needed.

Overview

The local adapter runs the complete SirSluginston stack on your machine using JSON files as the database, your local filesystem for media, and a dev auth stub. No cloud account required.

This is your development and evaluation environment. When you're ready to deploy, run the AWS or GCP adapter to provision real cloud infrastructure without losing your content.

What Was Provisioned

Database: .sirsluginston/ directory in your project root. Pages live in .sirsluginston/pages/<tenantId>/ as JSON files. Config lives in .sirsluginston/config/<tenantId>.json.

Auth: Dev stub — any login with your LOCAL_ADMIN_EMAIL (set in .env.local) gets admin access. No real authentication occurs.

Media: Uploaded files stored in the local filesystem.

Beacon: Runs in local mode — shows a soft informational banner in the admin panel. No cloud enforcement, no license acceptance recording.

File Structure

your-project/
  .sirsluginston/
    pages/<tenantId>/     ← JSON page files
    config/<tenantId>.json ← brand config
  app/
    lib/
      data.ts             ← re-exports Core read/write
      admin-actions.ts    ← server actions
      user-actions.ts     ← user settings actions
    api/
      beacon-health/route.ts
      slime-agreement/route.ts
      upload/route.ts
    [...slug]/page.tsx     ← catch-all page renderer
  .env.local              ← your config (never commit)

Auth in Local Mode

Local mode uses a dev auth stub. Set LOCAL_ADMIN_EMAIL in your .env.local to the email address you want to use as admin. That email gets full admin access on login.

There is no real authentication — no Cognito, no tokens, no session validation beyond the email match. This is intentional and appropriate for local development. The cloud adapter replaces this with real authentication when you deploy.

Cloud Deployment

When you're ready to deploy:

AWS:

npx @sirsluginston/aws-adapter init

The AWS adapter will:

  1. Ask for your region, company name, domain, and add-ons
  2. Provision Lambda SSR, CloudFront, S3, DynamoDB, Cognito, Route53, and ACM
  3. Migrate your existing .sirsluginston/ content into DynamoDB — your pages and config carry over
  4. Show your initial solvency cap estimate

AWS Deployment Guide → · GCP Adapter (Coming Soon) →

Loading Advertisement...