feat: added dokuwiki

dokuwiki/docker-compose.yml

@@ -0,0 +1,14 @@
+---
+services:
+  dokuwiki:
+    image: linuxserver/dokuwiki:latest
+    container_name: dokuwiki
+    environment:
+      - PUID=1001
+      - PGID=1001
+      - TZ=Europe/Berlin
+    ports:
+      - "127.0.0.1:18443:443"
+    volumes:
+      - ./volumes/dokuwiki:/config
+    restart: unless-stopped

ntfy/README.md

@@ -16,14 +16,34 @@
 ```
 
 
+
 ## Config
 ```
+# Start container
+docker compose up -d && docker compose logs -f
+
+# Move config file into ntfy directory
+mv server.yml volumes/ntfy/
+
+# Restart ntfy container
+docker compose restart
+
+# Access the container shell
+docker compose exec -it ntfy sh
+
+# Create a admin
+ntfy user add --role=admin username
+# Create a user and grant read / write access to topic
+ntfy user add --role=user username
+ntfy access username topic rw
+
+# Create web push key pair
+# required for background push notification with webapp
+ntfy webpush keys
+
 # Edit ntfy config
 vi server.yml
 
-# Move file into ntfy directory
+# Restart ntfy container again
-mv server.yml volumes/ntfy
+docker compose restart
-
+```
-# Start ntfy container
-docker compose up -d
-```

ntfy/server.yml

@@ -165,10 +165,10 @@ attachment-cache-dir: /var/cache/ntfy/attachments
 # Create web push key pair inside the docker container:
 #   docker compose exec -it ntfy /bin/bash
 #   ntfy webpush keys
-web-push-public-key:
+# web-push-public-key:
-web-push-private-key:
+# web-push-private-key:
-web-push-file: /var/cache/ntfy/webpush.db
+# web-push-file: /var/cache/ntfy/webpush.db
-web-push-email-address: hostmaster@exmaple.com
+# web-push-email-address: hostmaster@exmaple.com
 # web-push-startup-queries:
 
 # If enabled, ntfy can perform voice calls via Twilio via the "X-Call" header.
@@ -229,7 +229,7 @@ enable-login: true
 #
 # iOS users:
 #   If you use the iOS ntfy app, you MUST configure this to receive timely notifications. You'll like want this:
-upstream-base-url: "https://ntfy.sh"
+# upstream-base-url: "https://ntfy.sh"
 #
 # If set, all incoming messages will publish a "poll_request" message to the configured upstream server, containing
 # the message ID of the original message, instructing the iOS app to poll this server for the actual message contents.