How-to guides

You have a specific job to do and you want the steps. Every page in this section leads with a working solution. Caveats, variations, and the reasoning come after it, or as a link.

These guides assume you already have a websocketd binary and have wrapped at least one script with it. If neither is true yet, work through the tutorial first.

Pick the group that matches what is in front of you. Reach for language fixes when your script misbehaves, deployment guides when the surrounding infrastructure does, and patterns when the problem belongs to neither and is really about shape.

When you want a precise fact instead of a procedure, the flag reference has it. When you want the reasoning behind a fix, output buffering and the process model cover most of it.

• Language-specific fixes — One page per language for the problem that dominates websocketd's issue history: a script that streams in a terminal but sends nothing, or everything at once, under websocketd.
• Deploy websocketd — Run websocketd behind a proxy, under an init system, in a container, and on a public address.
• Patterns — Recipes keyed to the shape of a problem rather than to a language or a deployment target.