feat: add Unraid installation documentation and update links

documentation/docs/install/getting_started.md

@@ -6,6 +6,7 @@ AdventureLog can be installed in a variety of ways. The following are the most c
 - [Proxmox LXC](proxmox_lxc.md) 🐧
 - [Synology NAS](synology_nas.md) ☁️
 - [Kubernetes and Kustomize](kustomize.md) 🌐
+- [Unraid](unraid.md) 🧡
 
 ### Other Options
 

documentation/docs/install/unraid.md

@@ -0,0 +1,22 @@
+# Installation with Unraid
+
+AdventureLog is available in the Unraid Community Applications store. You can install it by searching for "AdventureLog" in the Community Applications store.
+
+Communuity Applications Page: [AdventureLog on CA Store](https://unraid.net/community/apps?q=Adventurelog)
+
+## Installation Configuration
+
+## Backend
+
+- Cache is only for when you have your appdata share on a cache drive
+- For this example we call the container `server` so the the frntend can connect to it at `http://server:8000` although this can be named anything you like as long as the frontend is configured to connect to the correct address
+
+![/static/img/unraid-config-1.png](/static/img/unraid-config-1.png)
+
+## Frontend
+
+![/static/img/unraid-config-3.png](/static/img/unraid-config-3.png)
+
+## Database
+
+![/static/img/unraid-config-2.png](/static/img/unraid-config-2.png)

documentation/docs/troubleshooting/nginx_failed.md

@@ -1,5 +1,9 @@
 # Troubleshooting: `Starting nginx: nginx failed!` in the Backend Container
 
+::: tip
+As of 1-10-2024, this should be resolved in the latest version of AdventureLog. If you are still experiencing this issue, please reach out to the AdventureLog community on Discord or GitHub for further assistance.
+:::
+
 The AdventureLog backend container uses a built-in Nginx container with a built-in nginx config that relies on the name `server` to be the service name of the backend container. If the Nginx service fails to start in the backend container, the whole backend service will keep restarting and fail to start.
 
 **The primary reason for this error is changing the backend service name `server` to something different**