Community Apps

OpenRA dedicated server OpenRA is a project that recreates and modernizes the classic Command & Conquer real time strategy games. We have developed a flexible open source game engine (the OpenRA engine) that provides a common platform for rebuilding and reimagining classic 2D and 2.5D RTS games (the OpenRA mods).

This Docker will download and install the preferred version of OpenRCT2 (don't forget to put in the server version to download). ATTENTION: First Startup can take very long since it downloads the gameserver files! Manual Installation: You can also install a version manually but please be sure to put in the right version number of the file: ‘v0.2.3-develop-e4a2b1f9c’ if the source file is named like this: ‘OpenRCT2-0.2.3-develop-e4a2b1f9c-linux-x86_64.tar’, drop the file into the openrct2 directory and eventually restart the container to install it. Update Notice: If you want to update or downgrade the game simply change the version number. ATTENTION: The variables Admin Name & Admin Hash will only work on the first time you enter these, after that you must change it manually in ‘/SERVER_DIR/user-data/users.json’. NOTICE: If you got no IPv6 you will get an Error and a Warning in the log about that, you can ignore that the server runs just fine on IPv4.

This package contains and installs the OpenRGB Patch that needs to be installed in conjunction with the OpenRGB Docker container to take full controll over your RGB lighting. To see all the RGB devices you have to pass through the devices /sys/bus/i2c/device and /dev/i2c-0 to the OpenRGB Docker container and maybe all other /dev/i2c-X devices (where you have to replace X with the number from the device to pass through).

OpenSearch is a scalable, flexible, and extensible open-source software suite for search, analytics, and observability applications derived from Elasticsearch 7.10.2 and Kibana 7.10.2 and licensed under Apache 2.0. It consists of a search engine daemon (OpenSearch) and a user interface for data administration and visualizations (OpenSearch Dashboards). Make sure Opensearch has access rights to the "Log Data" folder. Permissions may need to be fixed with integrated Unraid File Manager. Steps below MUST be used in order to get Opensearch working correctly. Check support thread for more information. 1. Install CA User Scripts 2. Create a new script named "set_max_map_count" 3. Contents of script as follows: #!/bin/bash sysctl -w vm.max_map_count=262144 4. Set script schedule to At Startup of Array

Open-VM-Tools for running unRAID as a VM under ESXi.

An "all-in-one" docker for all your private browsing needs (including OpenVPN client with nftables kill switch ; Socks5 + HTTP proxy to both VPN and TOR (the onion router) ; DNS server to DoT (DNS-over-TLS) services). NOTE: you must place your own OpenVPN configuration to the host path that is mapped to /etc/openvpn (The ovpn file must be named openvpn.ovpn. Credentials + certs can be in the same file or split out into multiple files - the flexibility is yours.) Set DNS_SERVERS to 127.2.2.2 to use DNS-over-TLS (use google and cloudflare services by default). Your DNS query out of the VPN exit will also be encrypted for even more security. Set it to other services IP's will use normal unencrypted services. Set HOST_NETWORK to your Unraid server network in CIDR format e.g. 192.168.1.0/24. For more detailed instructions, refer to the support thread (https://forums.unraid.net/topic/96233-support-testdasi-repo/) or project page (https://github.com/testdasi/openvpn-client-aio).

An "all-in-one" docker for all your private browsing needs (including OpenVPN client with nftables kill switch ; Socks5 + HTTP proxy to the VPN ; DNS server to DoT (DNS-over-TLS) services). It's the same as OpenVPN AIO Client docker but without TOR. NOTE: you must place your own OpenVPN configuration to the host path that is mapped to /etc/openvpn (The ovpn file must be named openvpn.ovpn. Credentials + certs can be in the same file or split out into multiple files - the flexibility is yours.) Set DNS_SERVERS to 127.2.2.2 to use DNS-over-TLS (use google and cloudflare services by default). Your DNS query out of the VPN exit will also be encrypted for even more security. Set it to other services IP's will use normal unencrypted services. Set HOST_NETWORK to your Unraid server network in CIDR format e.g. 192.168.1.0/24. For more detailed instructions, refer to the support thread (https://forums.unraid.net/topic/96233-support-testdasi-repo/) or project page (https://github.com/testdasi/openvpn-client-aio).

This OpenVPN container was designed to be started first to provide a connection to other containers (using '--net=container:OpenVPN-Client'), see the documentation for further help here: https://github.com/ich777/docker-openvpn-client The basic steps for a OpenVPN connection that requires a Username and Password are: 1) Rename your *.ovpn to 'vpn.ovpn' and place it in your OpenVPN-Client directory, 2) Create in the same directory a file named 'vpn.auth' and place your Username in the first line and the Password for the connection in the second line and save it 3) Restart the container open the logs and see if the connection to your VPN establishes successfully. To tunnel traffic from another container through this container edit the template from the other container, set the 'Network Type' to: 'None', enable the advanced view in the top right corner and at 'Extra Parameters' add the following: '--net=container:OpenVPN-Client' (replace 'OpenVPN-Client' with the name of this container if you choose a different name for it) and write down the port(s) that you need to connect to. After that go back to edit this containers template and add the port that you have noted in the above step to this container and click 'Apply' now you can connect to the container that you tunneld the traffic though this container. You can route the traffic from multiple containers through this container with the steps above, if you need more ports then simply add more ports in this containers template. DNS: By default this container uses Googles DNS Server: 8.8.8.8 if you want to edit this turn on 'Advanced View' and edit this setting at 'Extra Parameters'. IPv6: By default IPv6 is disabled in this container. If you want to enable it turn on 'Advanced View' and delete the entry: '--sysctl net.ipv6.conf.all.disable_ipv6=1' from the 'Extra Parameters' or simply set it to: '--sysctl net.ipv6.conf.all.disable_ipv6=0'. ADVANCED CONFIG: If you leave the appdata directory for this container empty it will start up and you have to manually configure it with the builtin comand: 'openvpn.sh', see: https://github.com/ich777/docker-openvpn-client

OpenVPN Client with integrated (NZB)Hydra2-Deluge-Sabnzbd (and HTTP + SOCKS5 proxies). Now with a Web GUI quick launch. High-level instructions: (1) Create an appdata folder in host and create a openvpn subfolder. (2) Copy your OpenVPN configuration to the above openvpn subfolder (must include openvpn.ovpn + credentials + certs). (3) Don't forget to map /data in the docker to the host (you can map the parent or individual subfolders depending on needs). (4) Start docker (other apps should configure themselves on first run). DON'T FORGET THE OVPN FILE!!! Default password for deluge is deluge Set DNS_SERVERS to 127.2.2.2 to use DNS-over-TLS (use google and cloudflare services by default). Your DNS query out of the VPN exit will also be encrypted for even more security. Set it to other services IP's will use normal unencrypted services. Set HOST_NETWORK to your Unraid server network in CIDR format e.g. 192.168.1.0/24. For more detailed instructions, refer to the support thread (https://forums.unraid.net/topic/96233-support-testdasi-repo/) or project page (https://github.com/testdasi/openvpn-hydesa).

OpenVPN Client with integrated (NZB)Hydra2-RTorrent (Flood GUI)-Sabnzbd (and HTTP + SOCKS5 proxies). Now with a Web GUI quick launch. High-level instructions: (1) Create an appdata folder in host and create a openvpn subfolder. (2) Copy your OpenVPN configuration to the above openvpn subfolder (must include openvpn.ovpn + credentials + certs). (3) Don't forget to map /data in the docker to the host (you can map the parent or individual subfolders depending on needs). (4) Start docker (other apps should configure themselves on first run). DON'T FORGET THE OVPN FILE!!! Default login to flood is admin/flood Set DNS_SERVERS to 127.2.2.2 to use DNS-over-TLS (use google and cloudflare services by default). Your DNS query out of the VPN exit will also be encrypted for even more security. Set it to other services IP's will use normal unencrypted services. Set HOST_NETWORK to your Unraid server network in CIDR format e.g. 192.168.1.0/24. For more detailed instructions, refer to the support thread (https://forums.unraid.net/topic/96233-support-testdasi-repo/) or project page (https://github.com/testdasi/openvpn-hyrosa).

The username is openvpn You can find the auto-generated password in the docker logs with this command: docker logs -f OpenVPNAccessServer

Openvscode-server(https://github.com/gitpod-io/openvscode-server) provides a version of VS Code that runs a server on a remote machine and allows access through a modern web browser.

VS Code has traditionally been a desktop IDE built with web technologies. A few years back, people started patching it in order to run it in a remote context and to make it accessible through web browsers. These efforts have been complex and error prone, because many changes had to be made across the large code base of VS Code. Luckily, in 2019 the VS Code team started to refactor its architecture to support a browser-based working mode. While this architecture has been adopted by Gitpod and GitHub, the important bits have not been open-sourced, until now. As a result, many people in the community still use the old, hard to maintain and error-prone approach. At Gitpod, we've been asked a lot about how we do it. So we thought we might as well share the minimal set of changes needed so people can rely on the latest version of VS Code, have a straightforward upgrade path and low maintenance effort.  ⚠️ Be careful, each time you create or update the docker, everything is reset (except the share folder).

Wyoming protocol server for openWakeWord wake word detection system. There is NO WEB-UI to this container.

Opera(https://www.opera.com/) is a multi-platform web browser developed by its namesake company Opera. The browser is based on Chromium, but distinguishes itself from other Chromium-based browsers (Chrome, Edge, etc.) through its user interface and other features.

This Docker will download and install SteamCMD. It will also install Operation: Harsh Doorstop and run it. ATTENTION: First Startup can take very long since it downloads the gameserver files! Update Notice: Simply restart the container if a newer version of the game is available. You can also run multiple servers with only one SteamCMD directory!

A minimalist podcast synchronization server, for self-hosting your podcast listening / download history. This allows you to keep track of which episodes have been listened to. Previously known as Micro GPodder.

Orbital Sync synchronizes multiple Pi-hole instances for high availability (HA) using the built-in "teleporter". In other words, it performs a "backup" in the Pi-hole admin interface of your primary Pi-hole instance, and then "restores" that backup to any number of "secondary" Pi-holes also via their admin interface. As a result, it supports the synchronization of anything currently supported by Pi-hole's "teleporter". If you have more than one slave instance you can add extra variables for SECONDARY_HOST_2_BASE_URL: SECONDARY_HOST_2_PASSWORD: SECONDARY_HOST_3_BASE_URL: SECONDARY_HOST_3_PASSWORD: If one or all of your pihole instances use a custom path which isn't '/admin' (ie. you are running them behind a reverse proxy) you can specify a custom path with SECONDARY_HOST_X_PATH variable, where X is the slave numer or PRIMARY_HOST_PATH for the primary. There is no web UI for this app, check the logs to see if it has run successfully.

Orca Slicer(https://github.com/SoftFever/OrcaSlicer) is an open source slicer for FDM printers. OrcaSlicer is fork of Bambu Studio, it was previously known as BambuStudio-SoftFever, Bambu Studio is forked from PrusaSlicer by Prusa Research, which is from Slic3r by Alessandro Ranellucci and the RepRap community

Enjoy OrcaSlicer directly in your browser with this easy to use Docker container. This template has the minimum variables defined, but you can find additional details on the template at the URLs listed below. https://github.com/helfrichmichael/orcaslicer-novnc https://hub.docker.com/r/mikeah/orcaslicer-novnc

Your Media Server's one-stop shop! HTPC/Homelab services organizer, written in PHP. The new, upgraded official image for Organzir v2.

Oscam(https://git.streamboard.tv/common/oscam) is an Open Source Conditional Access Module software used for descrambling DVB transmissions using smart cards. It's both a server and a client.

osTicket is a widely-used open source support ticket system. It seamlessly integrates inquiries created via email, phone and web-based forms into a simple easy-to-use multi-user web interface. Manage, organize and archive all your support requests and responses in one place while providing your customers with accountability and responsiveness they deserve.

The fastest wiki and knowledge base for growing teams. More information https://docs.getoutline.com/s/hosting/doc/docker-7pfeLP5a8t Authentication used in the docker template is OpenID https://medium.com/@Lola_Dam/guide-for-installing-outline-with-authelia-as-an-openid-provider-129a141f6090

A self-hosted LaTeX editor

WireGuard VPN, Privoxy and Unbound built-in! Makes Sonarr and Radarr go into overdrive, without you doing a thing.

Overseerr(https://overseerr.dev/) is a request management and media discovery tool built to work with your existing Plex ecosystem.

Overseerr is a free and open source software application for managing requests for your media library. It integrates with your existing services such as Sonarr, Radarr and Plex!

openvpn with privoxy in docker with cron after docker start check your config folder, add your *.ovpn file(s) and edit logindata.conf LOCAL_NET - CIDR mask of the local IP addresses which will acess the proxy and bypass it, comma seperated OPENVPN_FILE - full path to ovpn file OVPN_SOCKS - set to off if not wanted OVPN_PRIVOXY - set to off if not wanted ONLINECHECK - set to off if not wanted ONLINECHECK_IP - default 8.8.4.4, change if wanted use privoxy on ip:8118 use socks on ip:1080

a xml grabber for enigma with open webif after docker start check your config folder and do your setups, setup is persistent, start from scratch by delete them cron options are updated on docker restart. cronjob changes doesnt require a restart. to test the cronjob functions docker exec -it dockername ./config/cronjob.sh