Community Apps

Create live TV channels from media on your Plex servers, and more! Access your channels by adding the spoofed Tunarr HDHomerun tuner to Plex, Jellyfin, or Emby. Or utilize generated M3U files with any 3rd party IPTV player app. Tunarr is a fork of dizqueTV. **Nvidia GPU Use:** Using the Unraid Nvidia Plugin to install a version of Unraid with the Nvidia Drivers installed and add **--runtime=nvidia** to "extra parameters" (switch on advanced view) and copy your **GPU UUID** to **NVIDIA_VISIBLE_DEVICES.** **Intel GPU Use:** Edit your **go** file to include **modprobe i915**, save and reboot, then add **--device=/dev/dri** to **"extra parameters"** (switch on advanced view)

FR: Statistiques monitorées vers écran compatibles. Le projet turing-smart-screen en container Docker. Plus d'informations sur les écrans compatibles et la configuration sur le github du projet: https://github.com/mathoudebine/turing-smart-screen-python EN: Monitor statistics on compatibles screens. Project turing-smart-screen in Docker. More informations about material compatibility and settings on the github's project link: https://github.com/mathoudebine/turing-smart-screen-python Setup: - setup variables and mapping - don't forget to modify the device name of your screen (see result of command dmesg just after connecting your screen) - if you need to add an nvidia GPU set same variables as Plex/emby/Jellyfin to work with Start: Look at the console if your screen didn't work. Customization: you will find on the /app's mapped folder the source of the project. On the res/ folder you will find a themes/ folder container some themes. You can take the name of a folder inside /app/res/themes and set it up to the THEME variable.

This is the official TuyaGateway 2.0 Docker

TVH-IPTV-Config - A simple IPTV config frontend for playlist filtering providing a M3U proxy for Plex, Emby, Jellyfin and (of course) Tvheadend. TVH-IPTV-Config (TIC) attempts to provide a simple IPTV config frontend for a Tvheadend (TVH) backend. In addition to this, it provides HDHomeRun tuner emulation, an HLS playlist proxy/caching and custom channel mapping from multipl playlist sources. Note: This template is a stand-alone installation of TIC and requires that you, the user, also install and maintain a seperate Tvheadend container. Currently, only TVH v4.3+ is tested and supported, though 4.2.8 may work fine. You will need to ensure you have the 'XMLTV URL grabber' module installed with your TVH server. If you want to run TIC without managing your own TVH backend, then you should look at using the "tvh-iptv" template which provides an AIO docker container solution. Features: Easily import/configure channels from playlists. Assign and locally cache logos per channel. Assign EPG sources for each channel. Configure channel numbers and ordering for channels. Configure multiple stream sources per channel. Manage and search through playlists that contain tens of thousands of streams without crashing the UI. Provide an ffmpeg buffer for your streams so multiple devices playing back the same stream will only use one playlist connection. Serve an HDHomeRun emulator for each playlist so Plex, Emby, and Jellyfin can connect to it an saturate the number of configured connections per playlist. Automatically fetch missing metada for your EPG programme schedule like icons, description, etc. Configure and automatically actively maintain a Tvheadend backend for IPTV without the fuss. Automatically generate IPTV networks in TVH per playlist configured with a number of connections allowed. Automatically manage a custom EPG based on channel selection. Automatically create muxes in TVH for each stream asssociated with a configured channel. Configure muxes with FFmpeg pipes to improve compatibility and provide a local buffer. Automatically map mux services to channels in TVH. Automaticlaly configure optimal streaming and timeseries settings. Automaticlaly configure optimal recording settings. Much more little tweaks behind the scenes... How it works: Tvheadend(https://www.tvheadend.org/), AKA "TVH", is a TV streaming server and recorder supporting, among other things, IPTV input sources. Tvheadend offers the HTTP (VLC, MPlayer), HTSP (Kodi, Movian) and SAT>IP streaming and there are a bunch of clients out there to use as clients for watching. The catch is that on its own, Tvheadend can be complicated to setup for IPTV. Once you read through all the documentation and forum posts on how to do it, it works well. But that is a steep learning curve. In addition to this, if you were to just throw a IPTV playlist of thousands of channels at the thing, well... good luck with that mess. To get it working really well, there is a lot of mouse clicking here and there and perhaps the odd ffmpeg pipe to configure on each MUX and... who as time for that! TIC should make life easy(ish) when setting up IPTV on Tvheadend. Advanced Configuration: LIMIT CPU USE: 1) Toggle this Docker Container template editor to "Advanced View". 2) In the "Extra Parameters" field, add "--cpus='1'". This value depends on the number of cores available to the container. To limit to 50%, set this value to 0.5 * n cores. If you have 2 cores available to this container, "--cpus='.5'" will equal 25% of that available CPU resources. To limit the CPU cores available to the continer, use "CPU Pinning" LIMIT RAM ALLOCATION: 1) Toggle this Docker Container template editor to "Advanced View". 2) In the "Extra Parameters" field, add "--memory='1g'". Tvheadend and TIC can use on average around 100Mib - 500 Mib of RAM for various tasks. Even though limiting RAM is unnecessary as this container should not ever need more that 1GB RAM it is good practice to do so.

Tvheadend(https://www.tvheadend.org/) works as a proxy server: is a TV streaming server and recorder for Linux, FreeBSD and Android supporting DVB-S, DVB-S2, DVB-C, DVB-T, ATSC, ISDB-T, IPTV, SATIP and HDHomeRun as input sources. Tvheadend offers the HTTP (VLC, MPlayer), HTSP (Kodi, Movian) and SATIP streaming. Multiple EPG sources are supported (over-the-air DVB and ATSC including OpenTV DVB extensions, XMLTV, PyXML).

Twingate makes Zero Trust Network Access easy to deploy, even easier to use, and always secure.

TwonkyMedia server (TMS) is DLNA-compliant UPnP AV server software from PacketVideo. TwonkyMedia server can be used to share and stream media to most UPnP AV or DLNA-compliant clients, in addition to non-UPnP devices through the HTML, RSS, and JSON supported front ends.

typecho PHP lightweight blog system docker for amd64/arm64 machine https://hub.docker.com/r/80x86/typecho/

Ubooquity(https://vaemendis.net/ubooquity/) is a free, lightweight and easy-to-use home server for your comics and ebooks. Use it to access your files from anywhere, with a tablet, an e-reader, a phone or a computer.

Ubuntu Playground (NO GUI) is a place where you can play with ubuntu command NOTE The data of the containter will be clear if you force update the container Click on the container icon then click console to access it

LXDE desktop ubuntu (use remote desktop client to connect)

This package contains the UGREEN LED Driver which will allow you to get your LEDs to work on your UGREEN NAS (please note that not all models are supported). The plugin is based on: https://github.com/miskcoo/ugreen_dx4600_leds_controller

This Plugin adds uinput to unRAID.

Umami is a simple, fast, privacy-focused alternative to Google Analytics. Requires a separate Postgresql container and external access via reverse proxy.

A tool to work around Sonarr, Radarr, Lidarr and Readarr's problems with foreign languages and symbols, like the German umlauts. Don't forget to update the URLs of your indexers in Prowlarr or directly in the used arr apps. Details are found in the documentation.

Unassigned Devices is used to mount and share non-array disks, remote SMB or NFS shares, and iso files.

Enables support in the Unassigned Devices Plugin for HFS+, exFAT, and apfs disk formats, and to enable destructive mode.

Unassigned Devices Preclear is used to exercise and clear disks and prepare them for adding to the array.

unbalanced transfers files/folders between disks in your array.

Unbound is a validating, recursive, and caching DNS resolver. It can be used to create your own recursive DNS-Server at home. You can use Unbound for services such as Pi-Hole (Here is a tutorial how to configure Pi-Hole with Unbound: https://www.youtube.com/watch?v=FnFtWsZ8IP0&t=695s) or you can create custom DNS Records for your local network.

Ungoogled Chromium(https://github.com/ungoogled-software/ungoogled-chromium) is Google Chromium, sans dependency on Google web services.

Ungoogled-Chromium is a lightweight approach to removing Google web service dependency from the Chromium project web browser. - Ungoogled Chromium is Google Chromium, sans dependency on Google web services. - Ungoogled Chromium retains the default Chromium experience as closely as possible. Unlike other Chromium forks that have their own visions of a web browser, Ungoogled Chromium is essentially a drop-in replacement for Chromium. - Ungoogled Chromium features tweaks to enhance privacy, control, and transparency. However, almost all of these features must be manually activated or enabled. For more details, see Feature Overview. You can find the full source code here: https://github.com/Eloston/ungoogled-chromium

Use the UniFi Controller software to quickly configure and administer an enterprise Wi‐Fi network. RF map and performance features, real-time status, automatic UAP device detection, and advanced security options are all seamlessly integrated.

The API Browser lets you pull raw, JSON formatted data from the API running on your UniFi Controller. Connecting to Multiple UniFi Controllers: Unifi-API-Browser supports multiple controllers. To use them create a copy of 'users-tempalte.php' and 'config-template.php' and mount them as volumes at '/app/config/config.php' & '/app/config/users.php'

SSH to your config folder (/mnt/user/appdata/unifi-cam-proxy) Run: openssl ecparam -out /tmp/private.key -name prime256v1 -genkey -noout openssl req -new -sha256 -key /tmp/private.key -out /tmp/server.csr -subj "/C=TW/L=Taipei/O=Ubiquiti Networks Inc./OU=devint/CN=camera.ubnt.dev/[email protected]" openssl x509 -req -sha256 -days 36500 -in /tmp/server.csr -signkey /tmp/private.key -out /tmp/public.key cat /tmp/private.key /tmp/public.key > client.pem rm -f /tmp/private.key /tmp/public.key /tmp/server.csr to create an cert for your cam. Get a token: https://{NVR IP}/proxy/protect/api/cameras/manage-payload Modify the Post Parameters to your needs. (check documentation)

The Unifi-controller(https://www.ubnt.com/enterprise/#unifi) software is a powerful, enterprise wireless software engine ideal for high-density client deployments requiring low latency and high uptime performance.

The Unifi-network-application(https://ui.com/) software is a powerful, enterprise wireless software engine ideal for high-density client deployments requiring low latency and high uptime performance.

Collect ALL UniFi Controller, Device and Client Data - Export to InfluxDB or Prometheus. Visualize with Grafana using included dashboards IMPORTAT! ACTION REQUIRED As of UniFi Poller version 2 all of the environment variables and config file format changed. You must reconfigure this container after you upgrade READ THE INSTRUCTIONS https://github.com/unifi-poller/unifi-poller/wiki/Configuration

A Python based tool for backing up UniFi Protect event clips as they occur to cloud storage. By default it will backup clips locally to /data inside the container. However you can create an rclone config file to backup to dozens of cloud providers. You can do this by running the following commands: $ mkdir -p /mnt/user/appdata/unifi-protect-backup/config $ docker run -it --rm -v /mnt/user/appdata/unifi-protect-backup/config:/root/.config/rclone --entrypoint rclone ghcr.io/ep1cman/unifi-protect-backup config Use the interactive configuration tool to setup your desired backup destination. Once complete you can start the container ensuring that the RCLONE_DESTINATION uses the name of your rclone remote e.g MyDropbox:/path/on/dropbx NOTE: If you are using the local remote type, the path set in RCLONE_DESTINATION will be inside the container so please use `/data`. You then need to set the optional "Clip directory" below to where you actually want the data to be stored.

Run UniFi Protect in Docker on x86 hardware. UniFi stopped supporting x86 at 1.13.3, so there will be no more updates. Must use Protect mobile app 1.3.8 to connect to this via UniFi Cloud on your phone. Run either as host networking mode, or custom br0 if you have other conflicting ports in use already via host mode - bridge mode does not work.