skrift-multisite

Configure ASGI-based multisite routing for Skrift deployments with shared resources.

1|3|Updated Jun 17, 2025
One-click install
npx skills add https://github.com/Smarter-Dev/smarter-dev --skill skrift-multisite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skrift-multisite
Source: https://github.com/Smarter-Dev/smarter-dev/tree/main/smarter_dev/.claude/skills/skrift-multisite
Command: npx skills add https://github.com/Smarter-Dev/smarter-dev --skill skrift-multisite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing multiple subdomains from a single deployment often leads to duplicated configurations and inconsistent user experiences. Skrift-multisite centralizes routing, authentication, and state while isolating site-specific controllers and themes.

Core Features & Use Cases

  • Centralized ASGI-based site dispatch
  • Shared database, session cookie, and middleware across subdomains
  • Site-specific controllers and themes for each subdomain
  • Use case: run blog.example.com, docs.example.com, and the primary domain from one deployment with consistent auth and data

Quick Start

Deploy a Skrift multisite setup and begin serving multiple subdomains from the same instance.

Frequently Asked Questions about skrift-multisite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I serve multiple subdomains from a single ASGI deployment with shared auth?

You can serve multiple subdomains from a single ASGI deployment by using centralized site dispatch to route requests while sharing database, session cookies, and middleware across all subdomain controllers.

How does shared session management work across different subdomains?

Shared session management works across subdomains by configuring a global cookie domain in your deployment, allowing users to maintain authenticated sessions seamlessly when navigating between sites like a blog and docs.

Can I isolate site controllers and themes while sharing a database in a multisite setup?

Yes, you can isolate site controllers and themes for each subdomain while sharing a database by defining site-specific configurations that separate presentation layers from centralized data and auth resources.

What do I need to configure to enable multisite routing for subdomains?

To enable multisite routing, you need to configure domain settings, site definitions in app.yaml, a global cookie domain, wildcard allowed_redirect_domains, and ASGI-based site dispatch rules.

Does Litestar support ASGI-based site dispatch for multiple domains?

Litestar supports ASGI-based site dispatch for multiple domains, allowing a single deployment instance to handle routing, shared resources, and subdomain isolation natively within its framework architecture.

Why do I need wildcard allowed_redirect_domains in a multisite architecture?

Wildcard allowed_redirect_domains are needed in a multisite architecture to securely manage authentication redirects across dynamically configured subdomains without requiring manual allowlist updates for each new site.