go-to-production

Codify Durable Streams production deployment checks into a repeatable checklist.

1.7k|64|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/durable-streams/durable-streams --skill go-to-production
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-to-production
Source: https://github.com/durable-streams/durable-streams/tree/main/packages/client/skills/go-to-production
Command: npx skills add https://github.com/durable-streams/durable-streams --skill go-to-production

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and codifies the production readiness process for Durable Streams, reducing the risk of misconfigurations and outages when moving from development to production.

Core Features & Use Cases

  • Production deployment checks: verify server deployment, switching to the Caddy production server, TLS configuration, and persistence settings.
  • Caching and header controls: enforce CDN-friendly Cache-Control and ETag headers, and preserve Stream-Cursor semantics to prevent cache collisions.
  • Lifecycle governance: ensure TTL or Expires-At is set (but not both) and provide guardrails for error handling on live streams, including request collapsing and CORS considerations.

Quick Start

Follow this checklist to switch from the development server to the Caddy production setup and enable proper caching, TLS, and stream lifecycle controls before deployment.

Frequently Asked Questions about go-to-production

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

FAQPage Schema
How do I configure a Durable Streams production deployment with HTTPS and Caddy?

Configuring a Durable Streams production deployment involves switching from the development server to the Caddy production setup. This checklist verifies your server deployment, TLS configuration, and persistence settings before going live.

What is production readiness for streaming applications?

Production readiness for streaming applications means ensuring server deployment, HTTPS, CDN caching, and stream lifecycle controls are correctly configured. This process codifies deployment best practices into a repeatable checklist to reduce misconfiguration risks.

How do I manage Cache-Control headers and Stream-Cursor semantics for CDN caching?

Managing CDN caching for Durable Streams requires enforcing Cache-Control and ETag headers while preserving Stream-Cursor semantics. This prevents cache collisions and ensures CDN-friendly content delivery.

How should I handle TTL and Expires-At lifecycle controls for live streams?

Handling live stream lifecycle controls requires ensuring either a TTL or an Expires-At value is set, but not both. This provides governance and guardrails for error handling, request collapsing, and CORS considerations.

Does this production readiness checklist support projects migrating from development environments?

This production readiness checklist specifically applies to projects migrating from development to production environments. It automates the verification of deployment configurations to reduce the risk of outages.