update with prettier

Author: Patrick M

_posts/2020-07-16-hello-world.md

@@ -1,9 +1,9 @@
 ---
 layout: post
-title: 'Hello World!'
+title: "Hello World!"
 date: 2020-07-16 -0500
-category: 'General'
-tags: 'general'
+category: "General"
+tags: "general"
 ---
 
 Finally, I have a blog set up.

_posts/2021-03-04-angular-build-versioning.md

@@ -1,10 +1,10 @@
 ---
 layout: post
-title: 'Adding build versions in Angular'
+title: "Adding build versions in Angular"
 date: 2021-03-04 19:30:00 -0500
 edit: 2021-03-05 10:30:00 -0500
-category: 'CI/CD'
-tags: ['angular', 'pipeline', 'ops']
+category: "CI/CD"
+tags: ["angular", "pipeline", "ops"]
 ---
 
 Have you ever found yourself wondering which version of an SPA is running when you pull up your site? This was a problem I wanted to answer in my Angular SPA. Utilizing the `npm version` command in my build pipeline, I was able to include my pipeline build number in my app, significantly decreased troubleshooting time and version confusion.
@@ -33,17 +33,17 @@ Find your `environment` constant in `src/environments`. You should see two files
 
 ```js
 export const environment = {
-  appVersion: require('../../package.json').version,
+  appVersion: require("../../package.json").version,
   production: true,
-  base: 'area',
+  base: "area",
 };
 ```
 
 In the non-production environment though, I like to add a dev tag.
 
 ```js
 // comment
-appVersion: require('../../package.json').version + '--dev';
+appVersion: require("../../package.json").version + "--dev";
 ```
 
 This helps me remember if I'm in a non production environment, because there is nothing worse than troubleshooting a problem in the wrong environment.

_posts/2021-03-23-outlook-spam-rule.md

@@ -1,9 +1,9 @@
 ---
 layout: post
-title: 'Creating a super Outlook SPAM Rule'
+title: "Creating a super Outlook SPAM Rule"
 date: 2021-03-23 22:40:00 -0500
-category: 'General'
-tags: ['outlook', 'spam']
+category: "General"
+tags: ["outlook", "spam"]
 ---
 
 After signing up for several virtual conferences in 2020, I noticed my work inbox was becoming inundated with junk email. Now this being my work email, I don't use it for any personal correspondence, and frankly never respond to anyone outside of my work's domain. Using Outlook online's email rules, I was able to eliminate all SPAM from my inbox in one easy move.

_posts/2021-04-08-asp-net-core-server-setup.md

@@ -1,10 +1,10 @@
 ---
 layout: post
-title: 'ASP.Net Core initial server setup'
+title: "ASP.Net Core initial server setup"
 date: 2021-04-08 12:00:00 -0500
 edit: 2021-04-09 12:00:00 -0500
-category: 'Hosting'
-tags: ['server', 'pipeline', 'ops', '.net']
+category: "Hosting"
+tags: ["server", "pipeline", "ops", ".net"]
 ---
 
 I wanted to document some important steps I take setting up a new server for hosting ASP.Net Core apps. These steps change over time as versions and features change, but this post will serve as a good, general guide for things to consider and remember; both for myself and anyone else who stumbles across it!

_posts/2021-06-16-autostart-api-spa-app.md

@@ -2,8 +2,8 @@
 layout: post
 title: "Start a SPA and it's API in one click"
 date: 2021-06-16 12:00:00 -0500
-tags: ['powershell', 'windows terminal', 'angular', '.net']
-category: 'CI/CD'
+tags: ["powershell", "windows terminal", "angular", ".net"]
+category: "CI/CD"
 ---
 
 I've been using start or jump scripts for a long time to start up my API and SPA at the same time. With [project TYE](https://devblogs.microsoft.com/aspnet/introducing-project-tye/) on the horizon, I thought I would share more about my more simplistic, "poor man", implementation.

_posts/2022-12-18-debian-lxc-setup.md

@@ -1,9 +1,9 @@
 ---
 layout: post
-title: 'LXC: First commands on a new Debian CT'
+title: "LXC: First commands on a new Debian CT"
 date: 2022-12-18 00:00:00 -0500
-category: 'Service Setup'
-tags: ['proxmox', 'lxc', 'debian']
+category: "Service Setup"
+tags: ["proxmox", "lxc", "debian"]
 ---
 
 A list of the first commands I run on a new Debian LXC to homogenize and secure my new environment.
@@ -29,6 +29,7 @@ useradd -m -g users -G sudo patrick
 chsh -s /bin/bash patrick
 passwd patrick
 ```
+
 ## Make the CLI more fun
 
 ```bash
@@ -79,7 +80,7 @@ patrick ALL=(ALL) NOPASSWD: ALL
 ```
 
 > Once you've made the changes, you can restart the LXC and use SSH with your new user
-{: .prompt-tip }
+> {: .prompt-tip }
 
 ## Unattended Upgrades Configuration
 

_posts/2022-12-18-install-pihole-ha.md

@@ -1,9 +1,9 @@
 ---
 layout: post
-title: 'Pi-hole setup with High Availablity'
+title: "Pi-hole setup with High Availablity"
 date: 2022-12-18 01:00:00 -0500
-category: 'Service Setup'
-tags: ['pihole', 'setup', 'high availablity', 'dns', 'spam']
+category: "Service Setup"
+tags: ["pihole", "setup", "high availablity", "dns", "spam"]
 ---
 
 This is a step by step guide to set up Pi-hole in a high availability environment. Previously I was using a lone Raspberry Pi 3B to run Pi-hole. The issue with this setup was, if that pi went down, DNS was down on my network, which is definitely unacceptable. So let make it better!
@@ -34,7 +34,7 @@ When you run the install command, a GUI will appear. It will guide you through t
 pihole -a -p
 ```
 
-Lastly, you'll want to add your user to the pihole group so that you can edit configuration files without needing sudo. This will be useful later. 
+Lastly, you'll want to add your user to the pihole group so that you can edit configuration files without needing sudo. This will be useful later.
 
 ```bash
 sudo usermod -a -G pihole <username>
@@ -104,20 +104,18 @@ vrrp_instance pihole {
 }
 ```
 
-| Line | Description |
-|---|---|
-| 1 | The first thing to configure is the instance name. I have it set to `pihole`. |
-| 2 | You will need to decide the node's default disposition, whether it is the master node or a backup. Keep in mind, the node's disposition will change as necessary based on other nodes. If another node enters the cluster with a higher priority, it will always become the master node. |
-| 3 | The name of the interface that the virtual IP will be bound. Can be found using `ip a`. |
-| 5 | The priority will configure which node is the Master. The master node will always be the node with the highest priority |
-| 6 | The advertisement timespan in seconds. |
-| 7 | You will need to add the node's IP |
-| 8 | The other nodes IPs |
-
-
+| Line | Description                                                                                                                                                                                                                                                                              |
+| ---- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 1    | The first thing to configure is the instance name. I have it set to `pihole`.                                                                                                                                                                                                            |
+| 2    | You will need to decide the node's default disposition, whether it is the master node or a backup. Keep in mind, the node's disposition will change as necessary based on other nodes. If another node enters the cluster with a higher priority, it will always become the master node. |
+| 3    | The name of the interface that the virtual IP will be bound. Can be found using `ip a`.                                                                                                                                                                                                  |
+| 5    | The priority will configure which node is the Master. The master node will always be the node with the highest priority                                                                                                                                                                  |
+| 6    | The advertisement timespan in seconds.                                                                                                                                                                                                                                                   |
+| 7    | You will need to add the node's IP                                                                                                                                                                                                                                                       |
+| 8    | The other nodes IPs                                                                                                                                                                                                                                                                      |
 
 > Never set an IP reservation for the virtual IP, or set it as a static address for another device
-{: .prompt-warning }
+> {: .prompt-warning }
 
 Also keep in mind, this is set up for unicast, but can be configured for multicast. I just like to be explicit. You can find more details about [keepalived configuration here](https://keepalived.readthedocs.io/en/latest/configuration_synopsis.html).
 

_posts/2022-12-18-lxc-plex-setup.md

@@ -1,9 +1,9 @@
 ---
 layout: post
-title: 'LXC: Setting up Plex'
+title: "LXC: Setting up Plex"
 date: 2022-12-18 23:00:00 -0500
-category: 'Service Setup'
-tags: ['plex']
+category: "Service Setup"
+tags: ["plex"]
 ---
 
 After setting up a new server, I wanted to migrate my plex install to the more powerful machine. This will be a jump from an i3-2100 to an i5-12500T. A substantial leap in performance.
@@ -27,7 +27,7 @@ Final provisioned LXC environment is as follows:
 Mounting my media share from a storage device was easy enough, once I realized I had to make the container privileged. I configured `fstab` to automount the share when the environment started, and used a credential file stored in /root for security.
 
 > Privileged Container must be set to true to mount a network share
-{: .prompt-tip }
+> {: .prompt-tip }
 
 Lets start with the credential file. It's a simple file that needs to live somewhere fstab can access. I used /root because `fstab` will run as root so I know it will have access.
 
@@ -118,4 +118,4 @@ Then you should be able to copy the files and restart the service.
 
 ```bash
 sudo systemctl start plexmediaserver && systemctl status plexmediaserver
-```
+```

_posts/2023-01-01-lxc-docker-setup.md

@@ -1,9 +1,9 @@
 ---
 layout: post
-title: 'LXC: Installing Docker on a Debian CT'
+title: "LXC: Installing Docker on a Debian CT"
 date: 2023-1-1 12:00:00 -0500
-category: 'Service Setup'
-tags: ['proxmox', 'lxc', 'debian', 'docker']
+category: "Service Setup"
+tags: ["proxmox", "lxc", "debian", "docker"]
 ---
 
 A quick guide to getting docker running on a Debian CT
@@ -65,8 +65,7 @@ sudo usermod -aG docker $USER
 ```
 
 > You'll need to logout and log back in for the change to take effect
-{: .prompt-warning }
-
+> {: .prompt-warning }
 
 ## Installing Lazydocker
 
@@ -103,4 +102,4 @@ Now you can simply run it with the following command.
 
 ```bash
 lazydocker
-```
+```

_posts/2023-01-24-reverse-proxy-home-assistant.md

@@ -1,9 +1,9 @@
 ---
 layout: post
-title: 'Configuring Home Assistant for Reverse Proxy'
+title: "Configuring Home Assistant for Reverse Proxy"
 date: 2023-1-23 12:00:00 -0500
-category: 'Service Setup'
-tags: ['home assistant', 'traefik']
+category: "Service Setup"
+tags: ["home assistant", "traefik"]
 ---
 
 This is a quick reminder for the code that needs to be added to the Home Assistant configuration YAML to get things working with a reverse proxy.
@@ -16,13 +16,13 @@ In the terminal, edit the configuration YAML
 nano /config/configuration.yaml
 ```
 
-Now add the following formatted YAML to the configuration file. 
+Now add the following formatted YAML to the configuration file.
 
 ```yaml
 http:
   use_x_forwarded_for: true
   trusted_proxies:
-    - 192.168.1.10    #traefik
+    - 192.168.1.10 #traefik
 ```
 
-For more information, check out the documentation [here](https://www.home-assistant.io/integrations/http/#reverse-proxies)
+For more information, check out the documentation [here](https://www.home-assistant.io/integrations/http/#reverse-proxies)