lint

Author: davidnewhall

docs/pages/client/cloudflare.md

@@ -5,12 +5,16 @@
 
 Notifiarr client to the Internet at all. In other words, don't do any of this.** But you can if you want to access your local Notifiarr Client from the internet
 
-Many users use Cloudflare's "Cloudflare Tunnel" feature or additional Cloudflare security features to provide / protect external access to their Notifiarr Client box.  Specific configuration required for Cloudflare's various options are detailed below.
+Many users use Cloudflare's "Cloudflare Tunnel" feature or additional Cloudflare security features to
+provide / protect external access to their Notifiarr Client box.  Specific configuration required for
+Cloudflare's various options are detailed below.
 
 ## Cloudflare Tunnel
 
 !!! info
-    This assumes that you already have a Cloudflare Tunnel set up on your system. If you want to get started with Cloudflare Tunnels follow this YouTube guide first: [Cloudflare Tunnel: Creating Tunnels via GUI - Bypass CG-NAT by IBRACORP](https://www.youtube.com/watch?v=RUJy9fjoiy4)
+    This assumes that you already have a Cloudflare Tunnel set up on your system. If you want to get started
+    with Cloudflare Tunnels follow this YouTube guide first:
+    [Cloudflare Tunnel: Creating Tunnels via GUI - Bypass CG-NAT by IBRACORP](https://www.youtube.com/watch?v=RUJy9fjoiy4)
 
 1. Login to your Cloudflare teams account at [dash.teams.Cloudflare.com](https://dash.teams.Cloudflare.com/)
 1. Click **Tunnels** and then **configure** next to the Cloudflare Tunnel you would like to use

docs/pages/client/configuration.md

@@ -23,7 +23,9 @@ When a new docker image is deployed with an empty /config folder mounted, the ap
   - **The Notifiarr application uses the API key for bi-directional authorization between the Site and the Client.**
 
 !!! danger "Unraid Users"
-    You must configure the Notifiarr API Key in the Unraid Template/ Container Settings. If you wish to use Plex then you'll also need to set the Plex Token and Plex URL in the template as well. The other integrations can be defined in notifiarr.conf
+    You must configure the Notifiarr API Key in the Unraid Template/ Container Settings.
+    If you wish to use Plex then you'll also need to set the Plex Token and Plex URL in the template as well.
+    The other integrations can be defined in notifiarr.conf
 
 !!! info "Docker Users"
     Note that Docker Environmental Variables - and thus the Unraid Template - override the Config file.
@@ -93,7 +95,9 @@ Config File and Docker Environmental Variables are listed below
 - Environmental Variables take precedent over config file settings
 - Must provide an API key from [notifiarr.com](https://notifiarr.com).
   - **The Notifiarr application uses the API key for bi-directional authorization.**
-- You may provide multiple Sonarr, Radarr or Readarr instances using `DN_SONARR_1_URL`, `DN_SONARR_2_URL`, etc or by duplicating the starr block in the conf file. Note the header of `[[radarr]]`, `[[sonarr]]`, `[[readarr]]`, etc. is required.
+- You may provide multiple Sonarr, Radarr or Readarr instances using
+  `DN_SONARR_1_URL`, `DN_SONARR_2_URL`, etc or by duplicating the starr block in the conf file.
+  Note the header of `[[radarr]]`, `[[sonarr]]`, `[[readarr]]`, etc. is required.
 
 ### Client
 

docs/pages/client/gui.md

@@ -1,6 +1,7 @@
 # Notifiarr Client UI
 
-The Client UI is the preferred and recommended method of modifying the Notifiarr configuration file. Its GUI provides an easy and intuitive interface for all users to configure Applications for use with Notifiarr.
+The Client UI is the preferred and recommended method of modifying the Notifiarr configuration file.
+Its GUI provides an easy and intuitive interface for all users to configure Applications for use with Notifiarr.
 
 ---
 
@@ -143,8 +144,13 @@ As of March 8, 2022, there are no existing integrations, so this is for future u
 extra API keys. Whatever you want. Separate them with newlines or spaces.
 1. `Bind Address` - This is the IP and port the app will listen on. 0.0.0.0 means all IPs, and you should use that in almost all cases! Change the port if the default 5454 does not work for you.
 1. `URL Base` - This application serves HTTP on / by default. You can change that by typing in something else here.
-1. `Upstreams` - If Notifiarr client is behind a reverse proxy (swag, nginx, etc), then you should add that proxy IP here. You can also specify full networks. This controls which IP is written to the web server log file (requestor or x-forwarded-for header). It also allows the x-webauth-user header for proxy authentication. Separate with spaces or new lines.
-1. `Host ID` - The Host ID parameter is used to uniquely identify this client installation. Changing this value is discouraged; it should be found automatically. Do not copy this value to another Notifiarr client insallation.
+1. `Upstreams` - If Notifiarr client is behind a reverse proxy (swag, nginx, etc), then you should add that proxy IP here.
+    You can also specify full networks. This controls which IP is written to the web server log file (requestor or
+    x-forwarded-for header). It also allows the x-webauth-user header for proxy authentication.
+    Separate with spaces or new lines.
+1. `Host ID` - The Host ID parameter is used to uniquely identify this client installation.
+    Changing this value is discouraged; it should be found automatically.
+    Do not copy this value to another Notifiarr client insallation.
 1. `Parallel Threads` - Disabling this setting will make the application use fewer go routines (threads) when gathering data from configured applications. Spreads out CPU usage and lowers memory footprint.
 1. `Retries` - Sometimes connections to Notifiarr.com fail. This controls how many times each request will be attempted in case of failures.
 1. `Timeout` - This is the timeout for API requests to Notifiarr.com.

docs/pages/client/install.md

@@ -166,7 +166,9 @@ curl -sSL https://raw.githubusercontent.com/Notifiarr/notifiarr/main/userscripts
 
 ## Docker
 
-This project builds automatically in [Docker Cloud](https://hub.docker.com/r/golift/notifiarr) and creates [ready-to-use multi-architecture images](https://hub.docker.com/r/golift/notifiarr/tags). The `latest` tag is always a tagged release in GitHub.
+This project builds automatically in [Docker Cloud](https://hub.docker.com/r/golift/notifiarr) and creates
+[ready-to-use multi-architecture images](https://hub.docker.com/r/golift/notifiarr/tags).
+The `latest` tag is always a tagged release in GitHub.
 
 ### Compose
 

docs/pages/client/reverseProxy.md

@@ -1,17 +1,23 @@
 # Client Reverse Proxy Configuration
 
 !!! danger "Reverse Proxy Users"
-      None of this is required or necessary. **We recommend NOT exposing your Notifiarr client to the Internet at all. In other words, don't do any of this.** But you can if you want to access your local Notifiarr Client from the internet
+      None of this is required or necessary.
+      **We recommend NOT exposing your Notifiarr client to the Internet at all. In other words, don't do any of this.**
+      But you can if you want to access your local Notifiarr Client from the Internet.
 
-While you can certainly poke a hole your firewall and send the traffic directly to this app, it is recommended that you put it behind a reverse proxy if you're going to expose it. It's pretty easy.
+While you can certainly poke a hole your firewall and send the traffic directly to this app,
+it is recommended that you put it behind a reverse proxy if you're going to expose it. It's pretty easy.
 
-- You'll want to tune the `upstreams` and `urlbase` client settings for your environment
-  - If your reverse proxy IP is `192.168.3.45` then set `upstreams` in the Profile page of the local Notifiarr Client to `192.168.3.45/32`
-- The `urlbase` on the local Notifiarr Client configuration page can be left at `/`, but change it if you serve this app from a subfolder like `/notifiarr`
+- You'll want to tune the `upstreams` and `urlbase` client settings for your environment.
+  - If your reverse proxy IP is `192.168.3.45` then set `upstreams`
+    in the Profile page of the local Notifiarr Client to `192.168.3.45/32`
+- The `urlbase` on the local Notifiarr Client configuration page can be left at `/`,
+  but change it if you serve this app from a subfolder like `/notifiarr`.
 
 ## Cloudflare Users
 
-Cloudflare Firewall / ZeroTrust users - See [this wiki entry](../../pages/client/cloudflare.md) to ensure Notifiarr is allowed through Cloudflare
+If yuo use Cloudflare Firewall or ZeroTrust see
+[this wiki entry](../../pages/client/cloudflare.md) to ensure Notifiarr is allowed through Cloudflare.
 
 ## NGINX Subfolder Example