Added support for more configurations

README.md

@@ -10,11 +10,17 @@ In the container's docker arguments, set an environment variable DOCKER_MODS=lin
 
 If adding multiple mods, enter them in an array separated by |, such as DOCKER_MODS=linuxserver/mods:swag-dashboard|linuxserver/mods:swag-mod2
 
-# Usage
+## Internal access using `<server-ip>:81`
 
-Navigate to `dashboard.domain.com` from your LAN to view the dashboard.
+Add a mapping of `81:81` to swag's docker run command or compose
 
-You can remove the allow/deny in `/config/nginx/proxy-confs/dashboard.subdomain.com` to expose it (on a VPS for example), and instead protect it some other way (like Authelia for example).
+## Internal access using `dashboard.domain.com`
+
+Requires an internal DNS, add a rewrite of `dashboard.domain.com` to your server's IP address
+
+## External access using `dashboard.domain.com`
+
+Remove the allow/deny lines in `/config/nginx/proxy-confs/dashboard.subdomain.com`, and instead secure it some other way (like Authelia for example).
 
 ## Notes 
 - The application discovery scans the proxy configs and looks for the following structure in accordance with the samples:
@@ -25,6 +31,8 @@ You can remove the allow/deny in `/config/nginx/proxy-confs/dashboard.subdomain.
     proxy_pass $upstream_proto://$upstream_app:$upstream_port;
     ```
 - Either [Swag Maxmind mod](https://github.com/linuxserver/docker-mods/tree/swag-maxmind) or [Swag DBIP mod](https://github.com/linuxserver/docker-mods/tree/swag-dbip) are required to enable the geo location graph.
+- The host's fail2ban can be supported by mounting it to swag `- /path/to/host/fail2ban.sqlite3:/dashboard/fail2ban.sqlite3:ro`
+- The host's logs can be supported by mounting it to swag `- /path/to/host/logs:/dashboard/logs:ro`
 
 # Example
 ![Example](.assets/example.png)