Skip to content

Commit ae4d844

Browse files
author
Patrick M
committed
update with prettier
1 parent cc952a0 commit ae4d844

19 files changed

+85
-85
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
layout: post
3-
title: 'Hello World!'
3+
title: "Hello World!"
44
date: 2020-07-16 -0500
5-
category: 'General'
6-
tags: 'general'
5+
category: "General"
6+
tags: "general"
77
---
88

99
Finally, I have a blog set up.

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
layout: post
3-
title: 'Adding build versions in Angular'
3+
title: "Adding build versions in Angular"
44
date: 2021-03-04 19:30:00 -0500
55
edit: 2021-03-05 10:30:00 -0500
6-
category: 'CI/CD'
7-
tags: ['angular', 'pipeline', 'ops']
6+
category: "CI/CD"
7+
tags: ["angular", "pipeline", "ops"]
88
---
99

1010
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
3333

3434
```js
3535
export const environment = {
36-
appVersion: require('../../package.json').version,
36+
appVersion: require("../../package.json").version,
3737
production: true,
38-
base: 'area',
38+
base: "area",
3939
};
4040
```
4141

4242
In the non-production environment though, I like to add a dev tag.
4343

4444
```js
4545
// comment
46-
appVersion: require('../../package.json').version + '--dev';
46+
appVersion: require("../../package.json").version + "--dev";
4747
```
4848

4949
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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
layout: post
3-
title: 'Creating a super Outlook SPAM Rule'
3+
title: "Creating a super Outlook SPAM Rule"
44
date: 2021-03-23 22:40:00 -0500
5-
category: 'General'
6-
tags: ['outlook', 'spam']
5+
category: "General"
6+
tags: ["outlook", "spam"]
77
---
88

99
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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
layout: post
3-
title: 'ASP.Net Core initial server setup'
3+
title: "ASP.Net Core initial server setup"
44
date: 2021-04-08 12:00:00 -0500
55
edit: 2021-04-09 12:00:00 -0500
6-
category: 'Hosting'
7-
tags: ['server', 'pipeline', 'ops', '.net']
6+
category: "Hosting"
7+
tags: ["server", "pipeline", "ops", ".net"]
88
---
99

1010
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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
layout: post
33
title: "Start a SPA and it's API in one click"
44
date: 2021-06-16 12:00:00 -0500
5-
tags: ['powershell', 'windows terminal', 'angular', '.net']
6-
category: 'CI/CD'
5+
tags: ["powershell", "windows terminal", "angular", ".net"]
6+
category: "CI/CD"
77
---
88

99
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

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
layout: post
3-
title: 'LXC: First commands on a new Debian CT'
3+
title: "LXC: First commands on a new Debian CT"
44
date: 2022-12-18 00:00:00 -0500
5-
category: 'Service Setup'
6-
tags: ['proxmox', 'lxc', 'debian']
5+
category: "Service Setup"
6+
tags: ["proxmox", "lxc", "debian"]
77
---
88

99
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
2929
chsh -s /bin/bash patrick
3030
passwd patrick
3131
```
32+
3233
## Make the CLI more fun
3334

3435
```bash
@@ -79,7 +80,7 @@ patrick ALL=(ALL) NOPASSWD: ALL
7980
```
8081

8182
> Once you've made the changes, you can restart the LXC and use SSH with your new user
82-
{: .prompt-tip }
83+
> {: .prompt-tip }
8384
8485
## Unattended Upgrades Configuration
8586

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

Lines changed: 14 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
layout: post
3-
title: 'Pi-hole setup with High Availablity'
3+
title: "Pi-hole setup with High Availablity"
44
date: 2022-12-18 01:00:00 -0500
5-
category: 'Service Setup'
6-
tags: ['pihole', 'setup', 'high availablity', 'dns', 'spam']
5+
category: "Service Setup"
6+
tags: ["pihole", "setup", "high availablity", "dns", "spam"]
77
---
88

99
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
3434
pihole -a -p
3535
```
3636

37-
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.
37+
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.
3838

3939
```bash
4040
sudo usermod -a -G pihole <username>
@@ -104,20 +104,18 @@ vrrp_instance pihole {
104104
}
105105
```
106106

107-
| Line | Description |
108-
|---|---|
109-
| 1 | The first thing to configure is the instance name. I have it set to `pihole`. |
110-
| 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. |
111-
| 3 | The name of the interface that the virtual IP will be bound. Can be found using `ip a`. |
112-
| 5 | The priority will configure which node is the Master. The master node will always be the node with the highest priority |
113-
| 6 | The advertisement timespan in seconds. |
114-
| 7 | You will need to add the node's IP |
115-
| 8 | The other nodes IPs |
116-
117-
107+
| Line | Description |
108+
| ---- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
109+
| 1 | The first thing to configure is the instance name. I have it set to `pihole`. |
110+
| 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. |
111+
| 3 | The name of the interface that the virtual IP will be bound. Can be found using `ip a`. |
112+
| 5 | The priority will configure which node is the Master. The master node will always be the node with the highest priority |
113+
| 6 | The advertisement timespan in seconds. |
114+
| 7 | You will need to add the node's IP |
115+
| 8 | The other nodes IPs |
118116

119117
> Never set an IP reservation for the virtual IP, or set it as a static address for another device
120-
{: .prompt-warning }
118+
> {: .prompt-warning }
121119
122120
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).
123121

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
layout: post
3-
title: 'LXC: Setting up Plex'
3+
title: "LXC: Setting up Plex"
44
date: 2022-12-18 23:00:00 -0500
5-
category: 'Service Setup'
6-
tags: ['plex']
5+
category: "Service Setup"
6+
tags: ["plex"]
77
---
88

99
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:
2727
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.
2828

2929
> Privileged Container must be set to true to mount a network share
30-
{: .prompt-tip }
30+
> {: .prompt-tip }
3131
3232
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.
3333

@@ -118,4 +118,4 @@ Then you should be able to copy the files and restart the service.
118118

119119
```bash
120120
sudo systemctl start plexmediaserver && systemctl status plexmediaserver
121-
```
121+
```

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

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
layout: post
3-
title: 'LXC: Installing Docker on a Debian CT'
3+
title: "LXC: Installing Docker on a Debian CT"
44
date: 2023-1-1 12:00:00 -0500
5-
category: 'Service Setup'
6-
tags: ['proxmox', 'lxc', 'debian', 'docker']
5+
category: "Service Setup"
6+
tags: ["proxmox", "lxc", "debian", "docker"]
77
---
88

99
A quick guide to getting docker running on a Debian CT
@@ -65,8 +65,7 @@ sudo usermod -aG docker $USER
6565
```
6666

6767
> You'll need to logout and log back in for the change to take effect
68-
{: .prompt-warning }
69-
68+
> {: .prompt-warning }
7069
7170
## Installing Lazydocker
7271

@@ -103,4 +102,4 @@ Now you can simply run it with the following command.
103102

104103
```bash
105104
lazydocker
106-
```
105+
```

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
layout: post
3-
title: 'Configuring Home Assistant for Reverse Proxy'
3+
title: "Configuring Home Assistant for Reverse Proxy"
44
date: 2023-1-23 12:00:00 -0500
5-
category: 'Service Setup'
6-
tags: ['home assistant', 'traefik']
5+
category: "Service Setup"
6+
tags: ["home assistant", "traefik"]
77
---
88

99
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
1616
nano /config/configuration.yaml
1717
```
1818

19-
Now add the following formatted YAML to the configuration file.
19+
Now add the following formatted YAML to the configuration file.
2020

2121
```yaml
2222
http:
2323
use_x_forwarded_for: true
2424
trusted_proxies:
25-
- 192.168.1.10 #traefik
25+
- 192.168.1.10 #traefik
2626
```
2727
28-
For more information, check out the documentation [here](https://www.home-assistant.io/integrations/http/#reverse-proxies)
28+
For more information, check out the documentation [here](https://www.home-assistant.io/integrations/http/#reverse-proxies)

0 commit comments

Comments
 (0)