Pipe Bomb

Pipe Bomb is a self-hosted application delivered as an all-in-one Docker Compose stack that bundles its API backend server, web frontend, and an Nginx reverse…

  • Media Applications
  • Media Servers
  • Tools & Utilities
Pipe Bomb is a self-hosted application delivered as an all-in-one Docker Compose stack that bundles its API backend server, web frontend, and an Nginx reverse proxy under a single port, for self-hosters who want a turnkey, self-managed service.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

46/100 Fair

Maintained
73last commit 73 days ago
Popular
123 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 55 days ago

GitHub stars
3
Open issues
0
Last commit
2026-09-09
License
MIT
Activity
stale

Checked 21 days ago - source: GitHub (pipe-bomb/docker)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the pipe library with pip Run the install command for your system so Python can find the package. Without it, any script that tries to import pipe will fail with a module-not-found error. source
  • Docker Compose install Download docker-compose.yml from the pipe-bomb/docker repository, then run 'docker compose up -d'. Pipe Bomb is served on port 9193 and is configured via environment variables in the compose file. source
  • Installation Download docker-compose.yml from the GitHub repo and run `docker compose up -d`; the app is served on port 9193 and configured via environment variables. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which port should I expose for Pipe Bomb?

Pipe Bomb is available by default on port 9193. If using the single-container install, map host port 9193 to container port 80.

Do I need to set PUBLIC_URL when using a reverse proxy?

Only if CORS is causing issues. Set PUBLIC_URL to the exact URL you use to access Pipe Bomb.

Which Pipe Bomb volumes should I back up or keep on persistent storage?

Keep the data and secrets volumes on persistent storage, and keep resources if you want to retain cover art and thumbnails. Audio cache, plugin cache, and temp are safe to clear or do not need persistence.

How do I point Pipe Bomb at a local music library?

Set MUSIC_PATH to the local music directory. For the single-container install, bind-mount the host music path to /music as read-only.

Can I install Pipe Bomb without Docker Compose?

Use the single-container image with separate volume mounts for data, resources, caches, plugins, temp, and music. It is suitable for platforms such as Unraid and Portainer.

Answers sourced from github.com

Community

Collected 44 days ago - public community threads