A simple docker-compose based configuration to stand up a new HTPC w/ Plex, Deluge, Sonarr, Radarr and more!
PSA: Project has moved to GitLab. This repo will remain on Github as a mirror.
This is a simple docker-compose configuration to standup a new HTPC. It's based on running on an Ubuntu server, but could easily be adapted for other opertaing systems with Docker support.
It includes the following Services
This project was heavily inspired by the MediaBox project... Many Thanks!
sudo apt update
then sudo apt upgrade
sudo blkid
- Find the block ID of your media drivesudo mkdir /media/Media
- make the mount point/etc/fstab
: UUID=BC6617A366175D88 /media/Media ntfs-3g uid=1000,gid=1000,dmask=022,fmask=133 0 0
docker
group. See Post-installation steps for Linux
git clone https://gitlab.com/phikai/htpc-docker-standup.git
cp sample.env .env
.env
to match your environmentdocker-compose up -d
LOCALUSER=
- This is the local user of your linux account and account running dockerHOSTNAME=
- Hostame of the server, can be found by executing hostname
from command lineIP_ADDRESS=
- Local IP Address of the server, should be staticPUID=
- UID of the local user, can be found by executing id
from the command linePGID=
- GID of the local user, can be found by executing id
from the command linePMSTOKEN=
- The claim token for the server to obtain a real server token. If not provided, server is will not be automatically logged in. If server is already logged in, this parameter is ignored. You can obtain a claim token to login your server to your plex account by visiting https://www.plex.tv/claim
VPNUNAME=
- Your VPN username from PIA or TorGuard
VPNPASS=
- Your VPN password from PIA or TorGuard
VPNPROVIDER=
- Your VPN provider, name must match a folder specified in ovpn
. This defaults to pia
if you copied sample.env
.VPN_REMOTE=
- The remote server you want to connect to (must support port forwarding)CIDR_ADDRESS=
- IP/netmask entries which allow access to the server without requiring authorization. We recommend you set this only if you do not sign in your server. For example 192.168.1.0/24,172.16.0.0/16
will allow access to the entire 192.168.1.x
range and the 172.16.x.x
TZ=
- Set the timezone inside the container. For example: Europe/London
. The complete list can be found here: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
PMSTAG=
- Which version of Plex Media Server, available options: latest
, plexpass
and public
. You should use latest
unless you have special requirements or are a Plex Pass subscriber.EMAIL=
- Email address to be used for Let's Encrypt SSL certificate validation - [email protected]
DOMAIN=
- Public domain to use for accessing services via a public domain - server.domain.com
WATCHTOWER_EMAIL=
- Email address you'd like Watchtower to notify for any notifications - [email protected]
SMTP_FROM=
- From address that your SMTP server uses to send email - [email protected]
SMTP_SERVER=
- Servername of your SMTP server - smtp.domain.com
SMTP_PORT=
- Port that your SMTP server uses to connect - 587
SMTP_USER=
- Username that your SMTP server uses to authenticateSMTP_PASS=
- Password for your SMTP user to authenticateSPEEDTEST_INTERVAL=
- Number of seconds between tests to the Speedtest.net servicesTRAEFIK_AUTH=
- Basic Auth for the Traefik Admin htpasswd Generator
STACK_NAME=
- This is used to specify the appropriate network Traefik should use. See #13 for details.Potential Script to setup, renew and copy SSL for Plex
If this project has helped you in anyway, and you'd like to say thanks...
You can also gift a Plex Pass subscription as a great way to show your appreciation.
AFFILIATE DISCLOSURE: You can also support this project by purchasing a VPN Subscription via one of the links in this README.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.