mirror of
https://github.com/casjaysdevdocker/aria2
synced 2026-05-19 02:47:48 -04:00
4b80ec9839
Some checks failed
aria2 / release-aria2 (push) Failing after 6m58s
AI.md CLAUDE.md Dockerfile .env.scripts IDEA.md README.md rootfs/root/docker/setup/00-init.sh rootfs/root/docker/setup/01-system.sh rootfs/root/docker/setup/02-packages.sh rootfs/root/docker/setup/03-files.sh rootfs/root/docker/setup/04-users.sh rootfs/root/docker/setup/06-post.sh rootfs/root/docker/setup/07-cleanup.sh rootfs/usr/local/bin/entrypoint.sh rootfs/usr/local/etc/docker/functions/entrypoint.sh rootfs/usr/local/etc/docker/init.d/00-aria2c.sh TODO.AI.md
789 B
789 B
aria2 — THE WHAT
A single Alpine-based Docker image that provides a complete, self-hosted download solution: aria2c handles multi-protocol downloads (HTTP/HTTPS, FTP, SFTP, BitTorrent, Metalink) via a JSON-RPC daemon on port 6800, while AriaNg (a pure-static web UI bundled at build time) is served by nginx on port 80, which also reverse-proxies /jsonrpc and /rpc to aria2c so end users interact with a single port. BitTorrent peer traffic uses port 6888. The design is zero-config on first run: the container seeds /config/aria2/aria2.conf and /config/nginx/nginx.conf from baked-in optimized defaults, a tracker.sh helper refreshes the BitTorrent tracker list at each startup, and users who want RPC authentication simply set RPC_SECRET in the environment.