Skip to content

Deployment

stratolms init can select node, cloudflare, vercel or netlify:

Terminal window
stratolms init my-course --adapter cloudflare

The repository build matrix verifies adapter builds and locked-content output. It does not prove a deployed site’s HTTPS headers, CDN cache behavior, provider webhooks, email delivery, abuse controls or rollback procedure. Those are owner-operated release gates.

Every deployment needs STRATO_SECRET and PUBLIC_SITE_URL. Selling paid courses additionally needs a configured payment provider/product, the provider’s webhook secret, and working delivery/recovery configuration. Production builds also require ABUSE_CONTROLS_ACKNOWLEDGED=true after host/CDN rate limits are configured. Never place secrets in source, static output or container layers.

See Cloudflare details for the current Worker-specific setup. The Deploy to Cloudflare button starts from a generated standalone copy of the same starter. Other adapters continue through the CLI.