icey-server-operator

Build, validate, package, and operate the icey-server CLI using CMake presets and preflight checks.

51|13|Updated Dec 16, 2016
One-click install
npx skills add https://github.com/nilstate/icey-cli --skill icey-server-operator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: icey-server-operator
Source: https://github.com/nilstate/icey-cli/tree/main
Command: npx skills add https://github.com/nilstate/icey-cli --skill icey-server-operator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates risky, ad-hoc operation of the icey-server media stack by providing a single, repeatable operator workflow for building, validating, packaging, and running the CLI and its web UI with correct checks.

Core Features & Use Cases

  • Build and validate with reproducible conventions: Use the repo’s supported CMake presets and the deterministic --doctor preflight to reduce “it runs on my machine” drift.
  • Verify runtime behavior end-to-end: Follow the documented bring-up order across stream, record, and relay, including RTSP/TURN/TLS domains and the browser smoke contract.
  • Manage release and distribution artifacts safely: Validate staged install layouts and package-manager cutover outputs (tar/zip/deb/APT/Homebrew/AUR/Nix/Windows manifests) without emitting placeholder artifacts.

Quick Start

Run the machine-readable server preflight by executing the one-liner: go to the build directory and run the icey-server binary with the doctor flag against your intended configuration so you catch missing source and config issues before starting the operator flow.

Frequently Asked Questions about icey-server-operator

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

FAQPage Schema
How do I validate a WebRTC media server configuration before starting stream or relay modes?

Validate your WebRTC media server configuration by running the icey-server binary with the --doctor preflight flag from your build directory. This check catches missing source and config issues against your intended settings before starting stream, record, or relay operations.

What's the best way to package a WebRTC media server for APT, Homebrew, and AUR distribution?

Package a WebRTC media server for APT, Homebrew, and AUR using the repository's scripted artifact validation and checksum/manifest gates. This approach validates staged install layouts and package-manager cutover outputs without emitting placeholder artifacts.

How does the --doctor preflight check work for WebRTC server bring-up?

The --doctor preflight check works by running a machine-readable validation against your intended configuration to catch missing source and config issues. It ensures deterministic build shape via CMake presets and verifies runtime readiness before operator workflow execution.

Can I use CMake presets to build a deterministic media server binary for CI-like validation?

Yes, you can use the repository's supported CMake presets to build a deterministic media server binary for CI-like validation. This reduces environment drift and ensures the build shape matches canonical conventions for stream, record, and relay modes.

Do I need TURN and TLS configured to run browser smoke tests on a media server?

TURN and TLS paths are optional for browser smoke tests, but configuring them allows full validation of the browser smoke contract during bring-up. The operator workflow supports verifying RTSP, TURN, and TLS domains alongside standard stream, record, and relay modes.

Why are my media server release artifacts failing checksum validation?

Media server release artifacts fail checksum validation when staged install layouts or package-manager cutover outputs contain placeholder artifacts. Use the repository's canonical scripted artifact validation and manifest gates to ensure all tar, zip, deb, and package manager outputs are correctly built.