alexta69/metube: README-based editorial guide

alexta69/metube describes itself in the README as "Self-hosted video downloader for YouTube and other sites (web UI for yt-dlp)". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "MeTube", the README says: MeTube is a self-hosted web UI for yt-dlp, for downloading media from YouTube and dozens of other sites.. That establishes the project's stated boundary, not a production test.

The README's "MeTube" section gives a useful starting point for deciding whether the project fits: Download playlists and channels, with configurable output and download options.. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Download videos, audio, captions, and thumbnails from a browser UI.. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "📝 File Naming & yt-dlp". The source evidence includes: Enabling writeinfojson or writethumbnail in YTDLOPTIONS also writes a feed-level .info.json and thumbnail when you add a playlist or channel.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: docker run -d -p 8081:8081 -v /path/to/downloads:/downloads ghcr.io/alexta69/metube When the README contains no runnable command, this article does not invent one. Open its "🐳 Run using Docker" section and confirm system dependencies, default ports, and first-run initialization before using a public server.