Developer shares key lessons from 18 months building self-hosted media server Quven

·1 views

Software developer spent 18 months building Quven, a self-hosted media server for personal movie, TV, and documentary libraries, documenting hard-won lessons along the way. The project revealed that video playback compatibility is not a simple yes-or-no property of a file, but a negotiation between the source, the client, the network, and user settings. The developer settled on a priority hierarchy: direct play first, then remuxing if only the container is incompatible, and transcoding only as a last resort. Native clients were prioritized over a universal web-based approach, as different platforms have distinct playback capabilities and lifecycle constraints. Safe operation of FFmpeg — including process limits, cancellation, hardware acceleration fallbacks, and resource cleanup — was identified as a core product requirement, not a minor technical detail.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Docker-to-Kubernetes Image Workflow on Ubuntu Remains Unchanged Despite Runtime Shifts

Despite the removal of dockershim in 2022, the core workflow of building container images with Docker and deploying them on Kubernetes has not changed. Docker remains a reliable build tool, and Kubernetes continues to run OCI-compliant images regardless of whether the underlying node runtime is containerd or cri-dockerd. Best practices include using multi-stage Dockerfiles to minimize image size, tagging images with immutable version numbers instead of 'latest' to ensure reliable rollbacks, and configuring readiness probes to prevent traffic from reaching pods before the application is ready. Registry authentication must be explicitly configured via pull secrets, or pods will fail with an ImagePullBackOff error. Keeping the build tool, node runtime, and deployment manifests as distinct concerns allows developers to work without being affected by changes at the runtime layer.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Scrum Master Runs 3-Month Spec-Driven Dev Project Without Reading Code

A scrum master with a development background built a solo software project over three months using a spec-driven, AI-assisted workflow without directly reading the codebase. Instead of a separate task-management system, each ticket is stored as a YAML-fronted spec file that doubles as the design document, test contract, and backlog item. AI sub-agents implement and review code based solely on these spec files, with review dosage and model complexity calibrated per ticket's risk level. Lifecycle status transitions are enforced automatically via git hooks, preventing any manual or agent-driven shortcuts through the pipeline. The author presents this not as a universal methodology but as a working reference implementation others can adapt to their own projects.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Converts CMMC and NIST 800-171 Compliance Rules Into AI-Ready JSON

A developer built a Python pipeline that converts two major federal compliance frameworks — CMMC Level 1 and NIST SP 800-171 Rev 2 — from dense regulatory text into structured, machine-readable JSON rules. The pipeline pulls official source data, normalizes it into a SQLite schema, and attaches agent-guidance instructions designed to work directly as AI coding agent guardrails. The resulting dataset covers 125 controls across both frameworks and can also be integrated into CI/CD pipelines or GRC platforms. A key challenge during development was inconsistent data from NIST's export formats, including a silent bug caused by differing CVSS v2 and v3 JSON structures. The project aims to replace slow, manual compliance reviews with automated, AI-assisted checks for defense contractors and government-adjacent organizations.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer releases open-source GitHub Action to auto-detect broken links in docs

A developer has built urldn-link-check, an open-source GitHub Action and CLI tool designed to automatically scan Markdown documentation for broken links during continuous integration. The tool was created after the developer noticed that broken links in documentation often go unnoticed until users report them. It can be triggered on every push or pull request, catching issues before they are merged into production. Available under the MIT license, the project is published on both GitHub and npm and welcomes community contributions. It is the first tool in the broader URLDN open-source ecosystem, with more projects planned for the future.

0 comments Read more at DEV Community