Name and icon code blocks by real filename across the site
This commit is contained in:
@@ -48,7 +48,7 @@ Find the `workgroup` variable and name your workgroup (e.g., `workgroup = WORKGR
|
||||
|
||||
Then scroll to the end of the file and add the following configuration:
|
||||
|
||||
```properties
|
||||
```properties [smb.conf]
|
||||
[video]
|
||||
comment = Video folder
|
||||
path = /video
|
||||
@@ -145,7 +145,7 @@ sudo nano /smb/.credentials
|
||||
|
||||
Write:
|
||||
|
||||
```properties
|
||||
```properties [.credentials]
|
||||
username=smbuser
|
||||
password=password
|
||||
```
|
||||
|
||||
@@ -84,7 +84,7 @@ sudo nano compose.yml
|
||||
```
|
||||
Paste the following:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
dockge:
|
||||
@@ -130,7 +130,7 @@ Watchtower is a container that checks for updates and pulls new images automatic
|
||||
- Name the stack `watchtower`
|
||||
- Paste the config below into the default config area in Dockge
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
watchtower:
|
||||
@@ -158,7 +158,7 @@ services:
|
||||
|
||||
Then fill in the `.env` section in Dockge with the following:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
SCHEDULE=
|
||||
WH_URL=
|
||||
```
|
||||
@@ -170,7 +170,7 @@ WH_URL=
|
||||
|
||||
To have Watchtower monitor your other containers, add this to their `compose.yml`:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
labels:
|
||||
|
||||
- com.centurylinklabs.watchtower.enable=true
|
||||
|
||||
@@ -57,7 +57,7 @@ root
|
||||
|
||||
Open Dockge in your browser, click on `compose`, name the stack `swag`, and copy the following config:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
swag:
|
||||
@@ -101,7 +101,7 @@ networks:
|
||||
✨ __Tip:__
|
||||
Add the watchtower label to each container to enable automatic updates
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
#...
|
||||
@@ -113,7 +113,7 @@ services:
|
||||
|
||||
Then in the `.env` file:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
DOMAIN=
|
||||
DOMAINS=
|
||||
EMAIL=
|
||||
@@ -144,7 +144,7 @@ sudo nano /docker/swag/config/dns-conf/ovh.ini
|
||||
|
||||
You should see:
|
||||
|
||||
```properties
|
||||
```properties [ovh.ini]
|
||||
# Instructions: https://github.com/certbot/certbot/blob/master/certbot-dns-ovh/certbot_dns_ovh/__init__.py#L20
|
||||
# Replace with your values
|
||||
dns_ovh_endpoint = ovh-eu
|
||||
@@ -174,7 +174,7 @@ sudo nano /docker/swag/config/nginx/nginx.conf
|
||||
|
||||
Add the following line below the `http` section:
|
||||
|
||||
```nginx
|
||||
```nginx [nginx.conf]
|
||||
include /config/nginx/dbip.conf;
|
||||
```
|
||||
|
||||
@@ -201,7 +201,7 @@ sudo nano /docker/swag/config/nginx/dbip.conf
|
||||
|
||||
Make your changes ([see documentation](https://github.com/linuxserver/docker-mods/tree/swag-dbip)), or use the following example:
|
||||
|
||||
```nginx
|
||||
```nginx [dbip.conf]
|
||||
geoip2 /config/geoip2db/dbip-country-lite.mmdb {
|
||||
auto_reload 1w;
|
||||
$geoip2_data_continent_code continent code;
|
||||
@@ -249,18 +249,29 @@ Save and close the file. Restart the stack.
|
||||
|
||||
In the domain config files (see next section), you can enable or disable the whitelist or blacklist ([see documentation here](https://www.forum-nas.fr/threads/tuto-installer-swag-en-docker-reverse-proxy.15057/)). In our case, the whitelist allows only French requests. The blacklist blocks only the listed countries. We'll use the blacklist, like so:
|
||||
|
||||
```nginx
|
||||
```nginx [some-app.subdomain.conf]{11}
|
||||
server {
|
||||
listen 443 ssl;
|
||||
listen [::]:443 ssl;
|
||||
|
||||
server_name some-app.*;
|
||||
|
||||
include /config/nginx/ssl.conf;
|
||||
|
||||
client_max_body_size 0;
|
||||
|
||||
if ($geo-blacklist = no) { return 404; }
|
||||
|
||||
location / {
|
||||
include /config/nginx/proxy.conf;
|
||||
include /config/nginx/resolver.conf;
|
||||
|
||||
set $upstream_app some-app;
|
||||
set $upstream_port 1234;
|
||||
set $upstream_proto http;
|
||||
proxy_pass $upstream_proto://$upstream_app:$upstream_port;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Exposing Dockge
|
||||
@@ -284,7 +295,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/dockge.subdomain.conf
|
||||
|
||||
Configure it like this:
|
||||
|
||||
```nginx
|
||||
```nginx [dockge.subdomain.conf]
|
||||
## Version 2023/12/19
|
||||
|
||||
server {
|
||||
@@ -333,7 +344,7 @@ By default, SWAG doesn’t recognize the name "dockge". You’ll need to add Doc
|
||||
|
||||
Go to the SWAG stack, click `edit`, and modify the config file like this (note the `networks` section):
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: #...
|
||||
|
||||
@@ -76,7 +76,7 @@ Open Dockge, click **Compose**, and name the stack `wg_easy`.
|
||||
|
||||
Copy the following configuration:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
wg-easy:
|
||||
@@ -128,7 +128,7 @@ networks:
|
||||
- You can customize WireGuard and web UI ports.
|
||||
- Add a Watchtower label for automatic updates:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
wg-easy:
|
||||
# ...
|
||||
@@ -209,7 +209,7 @@ sudo cp ~/wg0.conf /docker/wireguard/config/wg_confs
|
||||
|
||||
Create the `compose.yaml` file in `/docker/wireguard`:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
wireguard:
|
||||
image: lscr.io/linuxserver/wireguard:latest
|
||||
|
||||
@@ -75,7 +75,7 @@ To generate the keys, we created the folders ahead of deployment using Dockge. D
|
||||
Open Dockge and search for "authentik" in the inactive stacks.
|
||||
Name the stack `authentik` and paste the following configuration, replacing `{AUTHENTIK_TAG:-2026.2}`{lang=properties} with [the latest version of Authentik](https://goauthentik.io/docs/releases).
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
|
||||
@@ -221,7 +221,7 @@ sudo nano /docker/swag/config/nginx/authentik-server.conf
|
||||
|
||||
Verify that the following variables are set correctly:
|
||||
|
||||
```nginx
|
||||
```nginx [authentik-server.conf]
|
||||
set $upstream_authentik authentik-server;
|
||||
proxy_pass http://$upstream_authentik:9000;
|
||||
```
|
||||
@@ -236,7 +236,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/auth.subdomain.conf
|
||||
|
||||
Paste the following configuration:
|
||||
|
||||
```nginx
|
||||
```nginx [auth.subdomain.conf]
|
||||
## Version 2023/05/31
|
||||
# Ensure your authentik container is named authentik-server
|
||||
# Ensure your DNS has a CNAME for authentik
|
||||
@@ -275,7 +275,7 @@ Save with :kbd{value="Ctrl+O"}, then :kbd{value="Enter"}, and exit with :kbd{val
|
||||
|
||||
Go to Dockge, and edit the SWAG compose file to add the Authentik network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -441,7 +441,7 @@ sudo nano /docker/authentik-outpost/compose.yaml
|
||||
```
|
||||
Paste the following configuration, updating the version in `{AUTHENTIK_TAG:proxy:2024.2.3}`{lang=properties} to match your Authentik server version.
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
version: "3.5"
|
||||
services:
|
||||
authentik_proxy:
|
||||
@@ -469,7 +469,7 @@ Go to the SWAG stack on the remote machine (or edit directly using Dockge) and a
|
||||
sudo nano /docker/swag/compose.yaml
|
||||
```
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: #...
|
||||
@@ -511,7 +511,7 @@ sudo nano /docker/authentik-outpost/.env
|
||||
|
||||
Paste the following configuration:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
HOST=
|
||||
TOKEN=
|
||||
```
|
||||
@@ -546,7 +546,7 @@ sudo nano /docker/swag/config/nginx/authentik-server.conf
|
||||
|
||||
In the file, change `authentik-server` to `authentik-outpost` as shown:
|
||||
|
||||
```nginx
|
||||
```nginx [authentik-server.conf]
|
||||
set $upstream_authentik authentik-outpost;
|
||||
proxy_pass http://$upstream_authentik:9000;
|
||||
```
|
||||
|
||||
@@ -99,7 +99,7 @@ sudo nano /docker/swag/config/tunnelconfig.yml
|
||||
|
||||
Paste:
|
||||
|
||||
```yaml
|
||||
```yaml [tunnelconfig.yml]
|
||||
ingress:
|
||||
|
||||
- hostname: mondomaine.fr
|
||||
@@ -125,7 +125,7 @@ sudo nano /docker/swag/config/nginx/nginx.conf
|
||||
|
||||
Add the following at the end of the `http` section:
|
||||
|
||||
```nginx
|
||||
```nginx [nginx.conf]
|
||||
real_ip_header X-Forwarded-For;
|
||||
real_ip_recursive on;
|
||||
include /config/nginx/cf_real-ip.conf;
|
||||
@@ -138,7 +138,7 @@ Save with :kbd{value="Ctrl+O"}, then :kbd{value="Enter"}, and exit with :kbd{val
|
||||
|
||||
In Dockge, edit your SWAG stack with this:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
swag:
|
||||
@@ -183,7 +183,7 @@ services:
|
||||
::tip{icon=""}
|
||||
✨ __Tip:__ Add a Watchtower label to automate updates:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
labels:
|
||||
|
||||
- com.centurylinklabs.watchtower.enable=true
|
||||
@@ -192,7 +192,7 @@ labels:
|
||||
|
||||
Fill in your `.env` file:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
PUID=
|
||||
PGID=
|
||||
DOMAIN=
|
||||
|
||||
@@ -32,7 +32,7 @@ root
|
||||
|
||||
Open Dockge, click on `compose`, name the stack `uptime-kuma`, then copy and paste the following:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
uptime-kuma:
|
||||
@@ -49,7 +49,7 @@ services:
|
||||
::tip{icon=""}
|
||||
✨ __Tip:__ Add the Watchtower label to each container to automate updates
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
uptime-kuma:
|
||||
#...
|
||||
@@ -90,7 +90,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/stats.subdomain.conf
|
||||
```
|
||||
Paste the following config:
|
||||
|
||||
```nginx
|
||||
```nginx [stats.subdomain.conf]
|
||||
## Version 2023/12/19
|
||||
|
||||
server {
|
||||
@@ -145,7 +145,7 @@ Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ct
|
||||
|
||||
In Dockge, edit the SWAG compose and add the Uptime-Kuma network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
|
||||
@@ -30,7 +30,7 @@ root
|
||||
|
||||
Open Dockge, click on `compose`, name the stack `dozzle`, then copy and paste the following:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
dozzle:
|
||||
@@ -53,7 +53,7 @@ services:
|
||||
::tip{icon=""}
|
||||
✨ __Tip:__ Add the watchtower label to each container to automate updates
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
dozzle:
|
||||
#...
|
||||
@@ -65,7 +65,7 @@ services:
|
||||
|
||||
Fill in your domain name in the `.env` file, for example:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
DOMAIN=dozzle.mydomain.com
|
||||
```
|
||||
|
||||
@@ -88,7 +88,7 @@ We assume you have created a subdomain like `dozzle.mydomain.com` in your [DNS z
|
||||
|
||||
Go to Dockge and edit the SWAG compose file to add Dozzle’s network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -123,7 +123,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/dozzle.subdomain.conf
|
||||
```
|
||||
Paste the configuration below:
|
||||
|
||||
```nginx
|
||||
```nginx [dozzle.subdomain.conf]
|
||||
## Version 2023/12/19
|
||||
|
||||
server {
|
||||
|
||||
@@ -44,7 +44,7 @@ Take note of the key.
|
||||
|
||||
Open Dockge, click on `compose`, name the stack `speedtest-tracker`, then paste the following:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
speedtest-tracker:
|
||||
@@ -75,7 +75,7 @@ id yourusername
|
||||
|
||||
In the `.env` file, set the variable `API_KEY` with the key you generated and add a cron-style test schedule, as well as your `PUID` and `GUID`, for example:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
SCHEDULE=15 */6 * * * # every 6 hours
|
||||
API_KEY=base64:zihejehkj8_nzhY/OjeieR= # your key
|
||||
PUID=1000
|
||||
@@ -110,7 +110,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/speedtest.subdomain.conf
|
||||
|
||||
Configure it like this:
|
||||
|
||||
```nginx
|
||||
```nginx [speedtest.subdomain.conf]
|
||||
## Version 2023/12/19
|
||||
|
||||
server {
|
||||
@@ -162,7 +162,7 @@ By default, SWAG doesn’t know the name "speedtest-tracker". To allow access, y
|
||||
|
||||
Go to Dockge, and edit SWAG’s compose to include Speedtest Tracker’s network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
|
||||
@@ -36,7 +36,7 @@ root
|
||||
|
||||
Open Dockge, click `compose`, name the stack `beszel`, and paste the following:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
beszel:
|
||||
@@ -69,7 +69,7 @@ services:
|
||||
::tip{icon=""}
|
||||
✨ __Tip:__ Add the Watchtower label to each container to automate updates.
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
beszel:
|
||||
#...
|
||||
@@ -81,7 +81,7 @@ services:
|
||||
|
||||
Fill out the `.env` file, for example:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
PORT=8090 # web UI port
|
||||
KEY= # private key to retrieve from Beszel when adding a system
|
||||
```
|
||||
@@ -115,7 +115,7 @@ You can also monitor a remote server. To do so, run the agent on the remote serv
|
||||
|
||||
Beszel will suggest a `compose.yaml` to deploy on the remote server, or you can use:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
beszel-agent:
|
||||
@@ -133,7 +133,7 @@ services:
|
||||
|
||||
And in `.env`:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
PORT=45876 # communication port between hub and remote agent
|
||||
KEY= # private key from Beszel when adding the system
|
||||
```
|
||||
@@ -162,7 +162,7 @@ You must have created a DNS subdomain like `beszel.mydomain.com` with a `CNAME`
|
||||
|
||||
In Dockge, edit Swag's compose file and add Beszel’s network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -198,7 +198,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/beszel.subdomain.conf
|
||||
|
||||
Paste:
|
||||
|
||||
```nginx
|
||||
```nginx [beszel.subdomain.conf]
|
||||
## Version 2023/12/19
|
||||
|
||||
server {
|
||||
|
||||
@@ -31,7 +31,7 @@ root
|
||||
|
||||
Open Dockge, click on `compose`, name the stack `upsnap`, then copy and paste the following:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
upsnap:
|
||||
@@ -60,7 +60,7 @@ services:
|
||||
::tip{icon=""}
|
||||
✨ __Tip:__ Add the watchtower label to each container to automate updates
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
upsnap:
|
||||
#...
|
||||
@@ -72,7 +72,7 @@ services:
|
||||
|
||||
Fill in the `.env`, for example:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
RANGE=192.168.1.0/24 # scans all devices on the local network with an IP between 192.168.0.1 and 192.168.1.255
|
||||
DNS=192.168.1.1 # DNS IP to resolve domain names, typically your router’s IP
|
||||
```
|
||||
@@ -101,7 +101,7 @@ We assume you've created a subdomain in your [DNS zone](/general/networking/dns)
|
||||
|
||||
Go to Dockge, and edit the SWAG compose by adding the UpSnap network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -136,7 +136,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/upsnap.subdomain.conf
|
||||
```
|
||||
And paste the following configuration:
|
||||
|
||||
```nginx
|
||||
```nginx [upsnap.subdomain.conf]
|
||||
## Version 2023/12/19
|
||||
|
||||
server {
|
||||
|
||||
@@ -58,7 +58,7 @@ mkdir -p /media/movies /media/library /media/tvseries
|
||||
Open Dockge in your browser and click `compose`.
|
||||
Name the stack `plex` and add the following config:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
linuxserver_plex:
|
||||
@@ -103,7 +103,7 @@ services:
|
||||
::tip
|
||||
✨ Add the Watchtower label to each container to automate updates:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
plex:
|
||||
#...
|
||||
@@ -127,7 +127,7 @@ id username
|
||||
|
||||
Fill in your `.env` file with the retrieved values, for example:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
PUID=1000
|
||||
GUID=1000
|
||||
```
|
||||
@@ -182,7 +182,7 @@ We assume you have the subdomain `tautulli.mydomain.com` with a `CNAME` pointing
|
||||
|
||||
Go to Dockge and edit SWAG’s compose file by adding Tautulli’s network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -219,7 +219,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/tautulli.subdomain.conf
|
||||
|
||||
Ensure the configuration matches the following, and edit it if needed:
|
||||
|
||||
```nginx
|
||||
```nginx [tautulli.subdomain.conf]
|
||||
## Version 2023/05/31
|
||||
# make sure that your tautulli container is named tautulli
|
||||
# make sure that your dns has a cname set for tautulli
|
||||
|
||||
@@ -55,7 +55,7 @@ mkdir -P /media/downloads
|
||||
|
||||
Open Dockge, click on `compose`, and name the stack `seedbox`. Paste the following config:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
|
||||
services:
|
||||
qbit:
|
||||
@@ -115,7 +115,7 @@ services:
|
||||
::tip{icon=""}
|
||||
✨ __Tip:__ Add the Watchtower label in each container to automate updates
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
qbittorrent:
|
||||
#...
|
||||
@@ -156,7 +156,7 @@ sudo nano /docker/gluetun/config.toml
|
||||
|
||||
Enter:
|
||||
|
||||
```toml
|
||||
```toml [config.toml]
|
||||
[[roles]]
|
||||
name = "t-anc/GSP-Qbittorent-Gluetun-sync-port-mod"
|
||||
routes = ["GET /v1/portforward"]
|
||||
@@ -168,7 +168,7 @@ Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ct
|
||||
|
||||
In Dockge, fill in the variables in `.env`:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
PUID=
|
||||
GUID=
|
||||
UI_PORT=
|
||||
@@ -227,7 +227,7 @@ We assume you have the subdomain `seedbox.mydomain.com` with a `CNAME` pointing
|
||||
|
||||
In Dockge, edit the SWAG compose file and add Gluetun’s network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -263,7 +263,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/seedbox.subdomain.conf
|
||||
|
||||
Paste the following config (check the port):
|
||||
|
||||
```nginx
|
||||
```nginx [seedbox.subdomain.conf]
|
||||
## Version 2023/12/19
|
||||
|
||||
server {
|
||||
|
||||
@@ -64,7 +64,7 @@ Without hardlinks, the _arr_ apps will copy the files instead—**doubling the s
|
||||
::
|
||||
|
||||
Open Docker and your `plex` stack. Modify the compose file as follows:
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
linuxserver_plex:
|
||||
@@ -198,7 +198,7 @@ services:
|
||||
::tip
|
||||
✨ Add the Watchtower label to each container to automate updates
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
plex:
|
||||
#...
|
||||
@@ -216,7 +216,7 @@ services:
|
||||
|
||||
Set your `.env` file with the variables below:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
PUID=
|
||||
GUID=
|
||||
MEDIA_PATH=
|
||||
@@ -420,7 +420,7 @@ We assume you have the subdomain `films.mydomain.com` with a `CNAME` pointing to
|
||||
|
||||
Go to Dockge, edit the SWAG compose file, and add the Overseerr network, which is the same as Plex (since it’s in the Plex stack):
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -456,7 +456,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/films.subdomain.conf
|
||||
|
||||
Paste the following:
|
||||
|
||||
```nginx
|
||||
```nginx [films.subdomain.conf]
|
||||
## Version 2024/07/16
|
||||
# make sure that your overseerr container is named overseerr
|
||||
# make sure that your dns has a cname set for overseerr
|
||||
|
||||
@@ -60,7 +60,7 @@ We assume that you have a subdomain `immich.yourdomain.com` with a `CNAME` point
|
||||
|
||||
In Dockge, open the SWAG stack and edit the compose file to add Immich's network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -96,7 +96,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/immich.subdomain.conf
|
||||
```
|
||||
Then paste the following configuration:
|
||||
|
||||
```nginx
|
||||
```nginx [immich.subdomain.conf]
|
||||
## Version 2023/12/19
|
||||
|
||||
server {
|
||||
|
||||
@@ -35,7 +35,7 @@ root
|
||||
|
||||
Open Dockge, click on `compose`, name the stack `nextcloud` and paste the following:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
nextcloud:
|
||||
@@ -69,7 +69,7 @@ id username
|
||||
|
||||
Then fill out the `.env` file with your preferred port and the values found above, for example:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
PUID=1000
|
||||
GUID=1000
|
||||
PORT=4545
|
||||
@@ -92,7 +92,7 @@ We assume you have a subdomain `nextcloud.yourdomain.com` with a `CNAME` pointin
|
||||
|
||||
In Dockge, go to your SWAG stack and edit the compose to add Nextcloud's network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -128,7 +128,7 @@ sudo nano /docker/nextcloud/config/www/nextcloud/config/config.php
|
||||
|
||||
Paste the following before the final `);`:
|
||||
|
||||
```php
|
||||
```php [config.php]
|
||||
'trusted_proxies' => [gethostbyname('swag')],
|
||||
'overwrite.cli.url' => 'https://nextcloud.example.com/',
|
||||
'overwritehost' => 'nextcloud.example.com',
|
||||
@@ -137,7 +137,7 @@ Paste the following before the final `);`:
|
||||
|
||||
Also add your domain in the `array` section. It should look like this:
|
||||
|
||||
```php
|
||||
```php [config.php]
|
||||
array (
|
||||
0 => '192.168.0.1:444', # This line may differ—don’t change it!
|
||||
1 => 'nextcloud.yourdomain.com', # Add your domain here
|
||||
@@ -154,7 +154,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/nextcloud.subdomain.conf
|
||||
|
||||
Paste the following:
|
||||
|
||||
```nginx
|
||||
```nginx [nextcloud.subdomain.conf]
|
||||
## Version 2024/04/25
|
||||
server {
|
||||
listen 443 ssl;
|
||||
|
||||
@@ -21,7 +21,7 @@ description: Install File Browser to browse and manage your server files from a
|
||||
## Installation
|
||||
Open Dockge, click on `compose`, name the stack `filebrowser`, then copy and paste the following:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
filebrowser:
|
||||
@@ -39,7 +39,7 @@ services:
|
||||
::tip{icon=""}
|
||||
✨ __Tip:__ Add the watchtower label to each container to automate updates.
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
filebrowser:
|
||||
#...
|
||||
@@ -72,7 +72,7 @@ __Pre-requisite:__ We assume you've already created a subdomain like `files.your
|
||||
|
||||
In Dockge, go to the SWAG stack and edit the compose file to add File Browser’s network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -104,7 +104,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/files.subdomain.conf
|
||||
|
||||
And paste the following configuration:
|
||||
|
||||
```nginx
|
||||
```nginx [files.subdomain.conf]
|
||||
## Version 2023/12/19
|
||||
|
||||
server {
|
||||
|
||||
@@ -21,7 +21,7 @@ description: Install Pingvin Share, a self-hosted file sharing platform to send
|
||||
## Installation
|
||||
Open Dockge, click `compose`, name the stack `pingvin`, then copy-paste this:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
pingvin-share:
|
||||
@@ -55,7 +55,7 @@ From here on, we assume the network name for Swag is `swag_default`.
|
||||
::tip{icon=""}
|
||||
✨ __Tip:__ Add the watchtower label to each container to automate updates.
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
pingvin-share:
|
||||
#...
|
||||
@@ -88,7 +88,7 @@ We assume you have the subdomain `pingvin.mydomain.com` with a `CNAME` pointing
|
||||
|
||||
In Dockge, go to the SWAG stack and edit the compose file to add the pingvin network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -124,7 +124,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/pingvin.subdomain.conf
|
||||
```
|
||||
Paste the configuration below:
|
||||
|
||||
```nginx
|
||||
```nginx [pingvin.subdomain.conf]
|
||||
## Version 2023/12/19
|
||||
|
||||
server {
|
||||
|
||||
@@ -37,7 +37,7 @@ root
|
||||
|
||||
Open Dockge, click on `compose`, name the stack `code-server`, and paste the following:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
code-server:
|
||||
@@ -63,7 +63,7 @@ services:
|
||||
::tip
|
||||
✨ Add the Watchtower label to each container to automate updates
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
code-server:
|
||||
#...
|
||||
@@ -87,7 +87,7 @@ id yourusername
|
||||
|
||||
Fill in the `.env` file with the values you found, for example:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
PW='$argon2i$v=19$m=4096,t=3,p=1$wST5QhBgk2lu1ih4DMuxvg$LS1alrVdIWtvZHwnzCM1DUGg+5DTO3Dt1d5v9XtLws4'
|
||||
PUID=1000
|
||||
GUID=1000
|
||||
@@ -108,7 +108,7 @@ __If it fails:__ check your firewall rules.
|
||||
## Mount Folders
|
||||
You can mount folders into VS Code by adding the relevant volumes in `compose.yaml` (or via Dockge), then redeploy the container.
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
code-server:
|
||||
#...
|
||||
@@ -128,7 +128,7 @@ __Preliminary:__ We assume you’ve created a subdomain like `code.yourdomain.co
|
||||
|
||||
In Dockge, go to the SWAG stack and edit the compose file to add code-server’s network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -164,7 +164,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/code.subdomain.conf
|
||||
|
||||
Paste the following configuration:
|
||||
|
||||
```nginx
|
||||
```nginx [code.subdomain.conf]
|
||||
## Version 2023/12/19
|
||||
|
||||
server {
|
||||
|
||||
@@ -30,7 +30,7 @@ root
|
||||
|
||||
Open Dockge, click on `compose`, name the stack `gitea`, and paste the following content:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
networks:
|
||||
gitea:
|
||||
@@ -59,7 +59,7 @@ services:
|
||||
|
||||
Fill out the `.env` file with the required information, for example:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
UID=1000
|
||||
GID=1000
|
||||
```
|
||||
@@ -81,7 +81,7 @@ __Prerequisite:__ We assume you have created a subdomain such as `gitea.yourdoma
|
||||
|
||||
In Dockge, go to the SWAG stack and edit the compose file by adding Gitea's network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -116,7 +116,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/gitea.subdomain.conf
|
||||
```
|
||||
Paste the configuration below:
|
||||
|
||||
```nginx
|
||||
```nginx [gitea.subdomain.conf]
|
||||
## Version 2023/12/19
|
||||
|
||||
server {
|
||||
@@ -183,7 +183,7 @@ sudo nano /docker/gitea/data/gitea/conf/app.ini
|
||||
|
||||
Then modify the server section with your domain information:
|
||||
|
||||
```properties
|
||||
```properties [app.ini]
|
||||
[server]
|
||||
DOMAIN = gitea.yourdomain.com
|
||||
SSH_DOMAIN = gitea.yourdomain.com
|
||||
|
||||
@@ -22,7 +22,7 @@ description: Install IT Tools, a self-hosted collection of handy utilities for d
|
||||
|
||||
Open Dockge, click on `compose`, name the stack `it-tools`, and paste the following:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
it-tools:
|
||||
@@ -37,7 +37,7 @@ services:
|
||||
::tip{icon=""}
|
||||
✨ __Tip:__ Add the Watchtower label to each container to enable automatic updates.
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
it-tools:
|
||||
#...
|
||||
@@ -64,7 +64,7 @@ __Pre-requisite:__ We assume you’ve created a subdomain like `tools.yourdomain
|
||||
|
||||
In Dockge, go to the SWAG stack and edit the compose file to add the IT Tools network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -105,7 +105,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/tools.subdomain.conf
|
||||
|
||||
Paste the configuration below:
|
||||
|
||||
```nginx
|
||||
```nginx [tools.subdomain.conf]
|
||||
## Version 2023/12/19
|
||||
|
||||
server {
|
||||
|
||||
@@ -59,7 +59,7 @@ Open Dockge and click `compose`
|
||||
|
||||
Name the stack `adguardhome` and paste the configuration below:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
adguardhome:
|
||||
@@ -83,7 +83,7 @@ services:
|
||||
::tip{icon=""}
|
||||
✨ __Tip:__ Add the watchtower label to each container to automate updates
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
adguardhome:
|
||||
# ...
|
||||
@@ -114,7 +114,7 @@ Do not use Cloudflare tunnels to expose AdGuard, and make sure any proxying is d
|
||||
|
||||
In Dockge, go to the SWAG stack and edit the compose file to add the AdGuard network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -151,7 +151,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/adguard.subdomain.conf
|
||||
|
||||
Paste the configuration below:
|
||||
|
||||
```nginx
|
||||
```nginx [adguard.subdomain.conf]
|
||||
## Version 2023/05/31
|
||||
# make sure that your adguard container is named adguard
|
||||
# make sure that your dns has a cname set for adguard
|
||||
|
||||
@@ -31,7 +31,7 @@ root
|
||||
|
||||
Open Dockge, click on `compose`, name the stack `vaultwarden`, and paste the following:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
vaultwarden:
|
||||
@@ -67,7 +67,7 @@ services:
|
||||
::tip{icon=""}
|
||||
✨ __Tip:__ Add the Watchtower label in each container to automate updates
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
vaultwarden:
|
||||
#...
|
||||
@@ -87,7 +87,7 @@ Copy the result securely.
|
||||
|
||||
In the `.env` file, enter the following variables:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
URL=
|
||||
TOKEN=
|
||||
```
|
||||
@@ -115,7 +115,7 @@ The main benefit of Vaultwarden is being able to access it remotely from any dev
|
||||
|
||||
In Dockge, go to the SWAG stack and edit the compose file to add the Vaultwarden network:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
swag:
|
||||
container_name: # ...
|
||||
@@ -151,7 +151,7 @@ sudo nano /docker/swag/config/nginx/proxy-confs/vault.subdomain.conf
|
||||
|
||||
And paste the following configuration:
|
||||
|
||||
```nginx
|
||||
```nginx [vault.subdomain.conf]
|
||||
server {
|
||||
listen 443 ssl;
|
||||
listen [::]:443 ssl;
|
||||
|
||||
@@ -9,7 +9,7 @@ navigation:
|
||||
:ellipsis{left=0px width=40rem top=10rem blur=140px zIndex=60}
|
||||
# Stockeex
|
||||
|
||||
```console
|
||||
```console [Terminal]
|
||||
sudo systemctl status stockeex-article
|
||||
currently writing, come back later...
|
||||
--
|
||||
|
||||
@@ -29,7 +29,7 @@ In short:
|
||||
|
||||
For example, with Beszel, the configuration would look like this:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
socat-proxy:
|
||||
image: git.djeex.fr/djeex/socat-proxy:latest
|
||||
|
||||
@@ -27,7 +27,7 @@ To allow **Backrest** to communicate securely with Docker, we’ll use [Docker S
|
||||
This avoids exposing the full Docker socket and grants only the necessary permissions.
|
||||
Here’s an example Docker stack:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
backrest:
|
||||
@@ -109,7 +109,7 @@ sleep 10
|
||||
|
||||
Once the scripts are in place and configured for the proper **Backrest** hooks, you just need to add the label `backrest.backup.stop=true` to the `compose.yaml` files of the containers that should stop and restart during backups:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
your_service:
|
||||
...
|
||||
|
||||
@@ -77,7 +77,7 @@ Open Dockge, click `compose`, and name the stack `wg_easy`.
|
||||
|
||||
Paste the following configuration:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
services:
|
||||
wg-easy:
|
||||
@@ -114,8 +114,8 @@ services:
|
||||
- You can also specify your own wireguard port with `WG_PORT`
|
||||
- Add the Watchtower label to enable automatic updates
|
||||
|
||||
```yaml
|
||||
services
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
wg-easy:
|
||||
#...
|
||||
labels:
|
||||
@@ -126,7 +126,7 @@ services
|
||||
|
||||
In `.env`:
|
||||
|
||||
```properties
|
||||
```properties [.env]
|
||||
HOST=
|
||||
PW=
|
||||
ADDRESS=
|
||||
@@ -210,7 +210,7 @@ sudo nano /docker/wireguard/compose.yaml
|
||||
|
||||
Paste:
|
||||
|
||||
```yaml
|
||||
```yaml [compose.yaml]
|
||||
services:
|
||||
wireguard:
|
||||
image: lscr.io/linuxserver/wireguard:latest
|
||||
|
||||
Reference in New Issue
Block a user