Remove tabs from yaml (librenms#14437)

* Remove tabs from yaml

* Remove tabs from random files

Author: Jellyfrog

.git-blame-ignore-revs

@@ -7,18 +7,18 @@
 
 # Apply fixes from StyleCI
 77c531527c0bf218038f8349e81f50d5386739a6
-82f43cb98dbe25d6e6fea4e787fa26aca898e41d	
+82f43cb98dbe25d6e6fea4e787fa26aca898e41d
 29f45ca352a8c5d5c308f93ce1240b7fdfc1c936
 2fc3a2121107c796cb0cf3e310c3a869a5b5798f
 
-# Fix coding style part 2 
+# Fix coding style part 2
 d8693f05ae4d9ec884cd2c2d850e7f78ba9dc2ae
 
-# Merge pull request #1449 from job/coding_style_old_files2 
+# Merge pull request #1449 from job/coding_style_old_files2
 61b14557ce45f8c6d90482075464aad1fae5e209
 
-# Merge pull request #1444 from job/coding_style_old_files2 
+# Merge pull request #1444 from job/coding_style_old_files2
 4ebabc634ab098d4f9721ea7f357baf029a6bf9c
 
-# Merge pull request #1431 from job/coding_style_old_files 
+# Merge pull request #1431 from job/coding_style_old_files
 89206b393978d8b42e3755698ca5542be7277270

AUTHORS.md

@@ -146,7 +146,7 @@ LibreNMS contributors:
 - Joseph Eames <[email protected]> (j-ems)
 - Eric Conroy <[email protected]> (NetworkNub)
 - Timothy Willey <[email protected]> (twilley)
-- Jon Ward	<[email protected]> (yon2004)
+- Jon Ward  <[email protected]> (yon2004)
 - Ian Viemeister <[email protected]> (iviemeister)
 - Thane Gill <[email protected]> (thanegill)
 - Christoffer Stokbæk <[email protected]> (stokbaek)

app/Plugins/ExamplePlugin/resources/views/device-overview.blade.php

@@ -9,8 +9,8 @@
                     <div class="col-sm-12">
                         {!! Str::markdown($device->notes ?? '') !!}
                     </div>
-		</div>
-	    </div>
-	</div>
+        </div>
+        </div>
+    </div>
     </div>
 </div>

app/Plugins/ExamplePlugin/resources/views/page.blade.php

@@ -3,6 +3,6 @@
         <div class="pull-left" style="margin-top: 5px;">
             <span style="font-size: 20px;">{{ $title }}</a></span><br>
             Description
-	</div>
+    </div>
     </div>
 </div>

doc/Extensions/Galera-Cluster.md

@@ -4,7 +4,7 @@ This is currently being tested, use at your own risk.
 
 LibreNMS can be used with a MariaDB Galera Cluster. This is a Multi Master cluster, meaning each
 node in the cluster can read and write to the database. They all have the same ability. LibreNMS will
-randomly choose a working node to read and write requests to. 
+randomly choose a working node to read and write requests to.
 
 
 For more information see
@@ -14,7 +14,7 @@ For more information see
 ## Getting Started
 
  * It is best practice to have a minimum of 3 nodes in the cluster, A odd number of nodes is recommended in the event nodes have a disagreement on data, they will have a tie breaker.
- * It's recommended that all servers be similar in hardware performance, cluster performance can be affected by the slowest server in the cluster. 
+ * It's recommended that all servers be similar in hardware performance, cluster performance can be affected by the slowest server in the cluster.
  * Backup the database before starting, and backing up the database regularly is still recommended even in a working cluster environment.
 
 ## Install and Configure Galera
@@ -52,20 +52,20 @@ wsrep_sst_method=rsync
 wsrep_node_address="192.168.1.35"
 wsrep_node_name="librenms1.35"
 ```
-Change the following values for your environment. 
+Change the following values for your environment.
 * wsrep_cluster_address -  All the IP address's of your nodes.
 * wsrep_cluster_name - Name of cluster, should be the same for all nodes
 * wsrep_node_address - IP address of this node.
 * wsrep_node_name - Name of this node.
 
 ### Edit LibreNMS .env
 
-LibreNMS supports up to 9 galera nodes, you define these nodes in the .env file. For each node we have the ability to define if this librenms installation/poller is able to write, read or both to that node. 
-The galera nodes you define here can be the same or differnt for each librenms poller. If you have a poller you only want to write/read to one galera node, you would simply add one DB_HOST, and omit all the rest. This allows you to precisely control what galera nodes a librenms poller is reading and or writing too. 
+LibreNMS supports up to 9 galera nodes, you define these nodes in the .env file. For each node we have the ability to define if this librenms installation/poller is able to write, read or both to that node.
+The galera nodes you define here can be the same or differnt for each librenms poller. If you have a poller you only want to write/read to one galera node, you would simply add one DB_HOST, and omit all the rest. This allows you to precisely control what galera nodes a librenms poller is reading and or writing too.
 
 * DB_HOST is always set to read/write.
 * DB_HOST must be set, however, it does not have to be the same on each poller, it can be different as long as it's part of the same galera cluster.
-* If the node that is set to DB_HOST is down, things like ```lnms db``` command no longer work, as they only use DB_HOST and don't failover to other nodes. 
+* If the node that is set to DB_HOST is down, things like ```lnms db``` command no longer work, as they only use DB_HOST and don't failover to other nodes.
 * Set DB_CONNECTION=mysql_cluster to enable
 * DB_STICKY can be used if you are pulling out of sync data form the database in a read request. For more information see
 <https://laravel.com/docs/database#the-sticky-option>
@@ -88,7 +88,7 @@ DB_USERNAME=librenms
 DB_PASSWORD=password
 ```
 The above .env on a librenms installation/poller would communicate to each galera node as follows.
- 
+
 * 192.168.1.35 - Read/Write
 * 192.168.1.36 - Read/Write
 * 192.168.1.37 - Read/Write
@@ -98,17 +98,17 @@ The above .env on a librenms installation/poller would communicate to each galer
 ### Starting Galera Cluster for the first time.
 
 1) Shutdown MariaDB server on ALL nodes.
-	```bash
-	sudo systemctl stop mariadb-server
-	```
+    ```bash
+    sudo systemctl stop mariadb-server
+    ```
 2) On the server with your existing database or any mariadb server if you are starting without existing data, run the following command
-	```bash
-	sudo galera_new_cluster
-	```
+    ```bash
+    sudo galera_new_cluster
+    ```
 3) Start the rest of the nodes normally.
-	```bash
-	sudo systemctl start mariadb-server
-	```
+    ```bash
+    sudo systemctl start mariadb-server
+    ```
 
 ### Galera Cluster Status
 
@@ -122,7 +122,7 @@ In the database run following mysql query
 SHOW GLOBAL STATUS LIKE 'wsrep_%';
 ```
 
-|    Variable Name                     |    Value                                                        |   Notes                                                 |  
+|    Variable Name                     |    Value                                                        |   Notes                                                 |
 |    :----:                            |    :----:                                                       |    :----:                                               |
 | -----------------------------------  | ----------------------------------------------------------------|---------------------------------------------------------|
 | wsrep_cluster_size                   | 2                                                               | Current number of nodes in Cluster                      |
@@ -150,6 +150,6 @@ seqno:   -1
 safe_to_bootstrap: 1
 ```
 
-If the safe_to_bootstrap = 1, then Galera determined that this node has the most up-to-date database and can be safeley used to start the cluster. 
+If the safe_to_bootstrap = 1, then Galera determined that this node has the most up-to-date database and can be safeley used to start the cluster.
 
 Once you have found a node that can be used for starting the cluster, follow the steps in starting for the first time.