You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+23-3Lines changed: 23 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,11 +10,11 @@ I am running it in Ubuntu Server 22.04; I also tested this setup on a [Synology
10
10
11
11

12
12
13
-
## Table of Content
13
+
## Table of Contents
14
14
15
15
<!-- TOC -->
16
16
*[Docker Compose NAS](#docker-compose-nas)
17
-
*[Table of Content](#table-of-content)
17
+
*[Table of Contents](#table-of-contents)
18
18
*[Applications](#applications)
19
19
*[Quick Start](#quick-start)
20
20
*[Environment Variables](#environment-variables)
@@ -26,6 +26,7 @@ I am running it in Ubuntu Server 22.04; I also tested this setup on a [Synology
26
26
*[qBittorrent](#qbittorrent)
27
27
*[Jellyfin](#jellyfin)
28
28
*[Homepage](#homepage)
29
+
*[Jellyseerr](#jellyseerr)
29
30
*[Traefik and SSL Certificates](#traefik-and-ssl-certificates)
30
31
*[Accessing from the outside with Tailscale](#accessing-from-the-outside-with-tailscale)
31
32
*[Optional Services](#optional-services)
@@ -59,6 +60,7 @@ I am running it in Ubuntu Server 22.04; I also tested this setup on a [Synology
59
60
|[PIA WireGuard VPN](https://github.com/thrnz/docker-wireguard-pia)| Encapsulate qBittorrent traffic in [PIA](https://www.privateinternetaccess.com/) using [WireGuard](https://www.wireguard.com/) with port forwarding. |[thrnz/docker-wireguard-pia](https://hub.docker.com/r/thrnz/docker-wireguard-pia)||
60
61
|[qBittorrent](https://www.qbittorrent.org)| Bittorrent client with a complete web UI<br/>Uses VPN network<br/>Using Libtorrent 1.x |[linuxserver/qbittorrent:libtorrentv1](https://hub.docker.com/r/linuxserver/qbittorrent)| /qbittorrent |
61
62
|[Jellyfin](https://jellyfin.org)| Media server designed to organize, manage, and share digital media files to networked devices |[linuxserver/jellyfin](https://hub.docker.com/r/linuxserver/jellyfin)| /jellyfin |
63
+
|[Jellyseer](https://jellyfin.org)| Manages requests for your media library |[fallenbagel/jellyseerr](https://hub.docker.com/r/fallenbagel/jellyseerr)| /jellyseer |
@@ -90,14 +92,16 @@ If you want to show Jellyfin information in the homepage, create it in Jellyfin
90
92
|`TIMEZONE`| TimeZone used by the container. |`America/New_York`|
91
93
|`DATA_ROOT`| Host location of the data files |`/mnt/data`|
92
94
|`DOWNLOAD_ROOT`| Host download location for qBittorrent, should be a subfolder of `DATA_ROOT`|`/mnt/data/torrents`|
93
-
|`PIA_LOCATION`| Servers to use for PIA|`ca` (Montreal, Canada) |
95
+
|`PIA_LOCATION`| Servers to use for PIA. [see list here](https://serverlist.piaservers.net/vpninfo/servers/v6)|`ca` (Montreal, Canada) |
94
96
|`PIA_USER`| PIA username ||
95
97
|`PIA_PASS`| PIA password ||
96
98
|`PIA_LOCAL_NETWORK`| PIA local network |`192.168.0.0/16`|
97
99
|`HOSTNAME`| Hostname of the NAS, could be a local IP or a domain name |`localhost`|
98
100
|`ADGUARD_HOSTNAME`| Optional - AdGuard Home hostname used, if enabled ||
99
101
|`ADGUARD_USERNAME`| Optional - AdGuard Home username to show details in the homepage, if enabled ||
100
102
|`ADGUARD_PASSWORD`| Optional - AdGuard Home password to show details in the homepage, if enabled ||
103
+
|`QBITTORRENT_USERNAME`| qBittorrent username to access the web UI |`admin`|
104
+
|`QBITTORRENT_PASSWORD`| qBittorrent password to access the web UI |`adminadmin`|
101
105
|`DNS_CHALLENGE`| Enable/Disable DNS01 challenge, set to `false` to disable. |`true`|
102
106
|`DNS_CHALLENGE_PROVIDER`| Provider for DNS01 challenge, [see list here](https://doc.traefik.io/traefik/https/acme/#providers). |`cloudflare`|
103
107
|`LETS_ENCRYPT_CA_SERVER`| Let's Encrypt CA Server used to generate certificates, set to production by default.<br/>Set to `https://acme-staging-v02.api.letsencrypt.org/directory` to test your changes with the staging server. |`https://acme-v02.api.letsencrypt.org/directory`|
@@ -110,6 +114,7 @@ If you want to show Jellyfin information in the homepage, create it in Jellyfin
110
114
|`LIDARR_API_KEY`| Lidarr API key to show information in the homepage ||
111
115
|`PROWLARR_API_KEY`| Prowlarr API key to show information in the homepage ||
112
116
|`JELLYFIN_API_KEY`| Jellyfin API key to show information in the homepage ||
117
+
|`JELLYSEERR_API_KEY`| Jellyseer API key to show information in the homepage ||
113
118
|`HOMEPAGE_VAR_TITLE`| Title of the homepage |`Docker-Compose NAS`|
114
119
|`HOMEPAGE_VAR_SEARCH_PROVIDER`| Homepage search provider, [see list here](https://gethomepage.dev/en/widgets/search/)|`google`|
115
120
|`HOMEPAGE_VAR_HEADER_STYLE`| Homepage header style, [see list here](https://gethomepage.dev/en/configs/settings/#header-style)|`boxed`|
@@ -212,6 +217,21 @@ Due to how the Docker socket is configured for the Docker integration, files mus
212
217
213
218
The files in `/homepage/tpl/*.yaml` only serve as a base to set up the homepage configuration on first run.
214
219
220
+
## Jellyseerr
221
+
222
+
Jellyseer gives you content recommendations, allows others to make requests to you, and allows logging in with Jellyfin credentials.
223
+
224
+
To setup, go to https://hostname/jellyseerr/setup, and set the URLs as follows:
225
+
- Jellyfin: http://jellyfin:8096/jellyfin
226
+
- Radarr:
227
+
- Hostname: radarr
228
+
- Port: 7878
229
+
- URL Base: /radarr
230
+
- Sonarr
231
+
- Hostname: sonarr
232
+
- Port: 8989
233
+
- URL Base: /sonarr
234
+
215
235
## Traefik and SSL Certificates
216
236
217
237
While you can use the private IP to access your NAS, how cool would it be for it to be accessible through a subdomain
0 commit comments