add posts and favicon, configure site

Author: binarypatrick

Gemfile.lock

@@ -0,0 +1,114 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    addressable (2.8.1)
+      public_suffix (>= 2.0.2, < 6.0)
+    colorator (1.1.0)
+    concurrent-ruby (1.1.10)
+    em-websocket (0.5.3)
+      eventmachine (>= 0.12.9)
+      http_parser.rb (~> 0)
+    ethon (0.16.0)
+      ffi (>= 1.15.0)
+    eventmachine (1.2.7)
+    ffi (1.15.5-x64-mingw-ucrt)
+    forwardable-extended (2.6.0)
+    html-proofer (3.19.4)
+      addressable (~> 2.3)
+      mercenary (~> 0.3)
+      nokogiri (~> 1.13)
+      parallel (~> 1.10)
+      rainbow (~> 3.0)
+      typhoeus (~> 1.3)
+      yell (~> 2.0)
+    http_parser.rb (0.8.0)
+    i18n (1.12.0)
+      concurrent-ruby (~> 1.0)
+    jekyll (4.3.1)
+      addressable (~> 2.4)
+      colorator (~> 1.0)
+      em-websocket (~> 0.5)
+      i18n (~> 1.0)
+      jekyll-sass-converter (>= 2.0, < 4.0)
+      jekyll-watch (~> 2.0)
+      kramdown (~> 2.3, >= 2.3.1)
+      kramdown-parser-gfm (~> 1.0)
+      liquid (~> 4.0)
+      mercenary (>= 0.3.6, < 0.5)
+      pathutil (~> 0.9)
+      rouge (>= 3.0, < 5.0)
+      safe_yaml (~> 1.0)
+      terminal-table (>= 1.8, < 4.0)
+      webrick (~> 1.7)
+    jekyll-archives (2.2.1)
+      jekyll (>= 3.6, < 5.0)
+    jekyll-paginate (1.1.0)
+    jekyll-redirect-from (0.16.0)
+      jekyll (>= 3.3, < 5.0)
+    jekyll-sass-converter (2.2.0)
+      sassc (> 2.0.1, < 3.0)
+    jekyll-seo-tag (2.8.0)
+      jekyll (>= 3.8, < 5.0)
+    jekyll-sitemap (1.4.0)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-theme-chirpy (5.3.2)
+      jekyll (~> 4.1)
+      jekyll-archives (~> 2.2)
+      jekyll-paginate (~> 1.1)
+      jekyll-redirect-from (~> 0.16)
+      jekyll-seo-tag (~> 2.7)
+      jekyll-sitemap (~> 1.4)
+    jekyll-watch (2.2.1)
+      listen (~> 3.0)
+    kramdown (2.4.0)
+      rexml
+    kramdown-parser-gfm (1.1.0)
+      kramdown (~> 2.0)
+    liquid (4.0.3)
+    listen (3.7.1)
+      rb-fsevent (~> 0.10, >= 0.10.3)
+      rb-inotify (~> 0.9, >= 0.9.10)
+    mercenary (0.4.0)
+    nokogiri (1.13.10-x64-mingw-ucrt)
+      racc (~> 1.4)
+    parallel (1.22.1)
+    pathutil (0.16.2)
+      forwardable-extended (~> 2.6)
+    public_suffix (5.0.1)
+    racc (1.6.1)
+    rainbow (3.1.1)
+    rb-fsevent (0.11.2)
+    rb-inotify (0.10.1)
+      ffi (~> 1.0)
+    rexml (3.2.5)
+    rouge (4.0.0)
+    safe_yaml (1.0.5)
+    sassc (2.4.0)
+      ffi (~> 1.9)
+    terminal-table (3.0.2)
+      unicode-display_width (>= 1.1.1, < 3)
+    thread_safe (0.3.6)
+    typhoeus (1.4.0)
+      ethon (>= 0.9.0)
+    tzinfo (1.2.10)
+      thread_safe (~> 0.1)
+    tzinfo-data (1.2022.7)
+      tzinfo (>= 1.0.0)
+    unicode-display_width (2.3.0)
+    wdm (0.1.1)
+    webrick (1.7.0)
+    yell (2.2.2)
+
+PLATFORMS
+  x64-mingw-ucrt
+
+DEPENDENCIES
+  html-proofer (~> 3.18)
+  jekyll-theme-chirpy (~> 5.3, >= 5.3.2)
+  tzinfo (~> 1.2)
+  tzinfo-data
+  wdm (~> 0.1.1)
+  webrick (~> 1.7)
+
+BUNDLED WITH
+   2.3.26

_config.yml

@@ -14,36 +14,35 @@ lang: en
 
 
 # Change to your timezone › http://www.timezoneconverter.com/cgi-bin/findzone/findzone
-timezone:
+timezone: America/New_York
 
 # jekyll-seo-tag settings › https://github.com/jekyll/jekyll-seo-tag/blob/master/docs/usage.md
 # ↓ --------------------------
 
-title: Chirpy                          # the main title
+title: BinaryPatrick                          # the main title
 
-tagline: A text-focused Jekyll theme   # it will display as the sub-title
+tagline: A development blog   # it will display as the sub-title
 
 description: >-                        # used by seo meta and the atom feed
-  A minimal, responsive, and powerful Jekyll theme for presenting professional writing.
+  A tutorial and notes driven blog for coding, development, and projects
 
 # fill in the protocol & hostname for your site, e.g., 'https://username.github.io'
-url: ''
+url: 'https://patrickmoore.dev'
 
 github:
-  username: github_username             # change to your github username
-
+  username: binarypatrick             # change to your github username
 twitter:
-  username: twitter_username            # change to your twitter username
+  username: binarypatrick            # change to your twitter username
 
 social:
   # Change to your full name.
   # It will be displayed as the default author of the posts and the copyright owner in the Footer
-  name: your_full_name
-  email: example@domain.com             # change to your email address
+  name: BinaryPatrick
+  # email: example@domain.com             # change to your email address
   links:
     # The first element serves as the copyright owner's link
-    - https://twitter.com/username      # change to your twitter homepage
-    - https://github.com/username       # change to your github homepage
+    - https://twitter.com/binarypatrick      # change to your twitter homepage
+    - https://github.com/binarypatrick       # change to your github homepage
     # Uncomment below to add more social links
     # - https://www.facebook.com/username
     # - https://www.linkedin.com/in/username
@@ -71,17 +70,17 @@ google_analytics:
 #     light  - Use the light color scheme
 #     dark   - Use the dark color scheme
 #
-theme_mode:   # [light|dark]
+theme_mode: dark  # [light|dark]
 
 # The CDN endpoint for images.
 # Notice that once it is assigned, the CDN url
 # will be added to all image (site avatar & posts' images) paths starting with '/'
 #
 # e.g. 'https://cdn.com'
-img_cdn:
+img_cdn: ''
 
 # the avatar on sidebar, support local or CORS resources
-avatar:
+avatar: 'https://pbs.twimg.com/profile_images/932787957894975488/X9_au0oQ_400x400.jpg'
 
 # boolean type, the global switch for ToC in posts.
 toc: true
@@ -109,7 +108,7 @@ comments:
 # Self-hosted static assets, optional › https://github.com/cotes2020/chirpy-static-assets
 assets:
   self_host:
-    enabled:      # boolean, keep empty means false
+    enabled:     # boolean, keep empty means false
     # specify the Jekyll environment, empty means both
     # only works if `assets.self_host.enabled` is 'true'
     env:          # [development|production]

_data/contact.yml

@@ -6,17 +6,17 @@
 -
   type: twitter
   icon: 'fab fa-twitter'
--
-  type: email
-  icon: 'fas fa-envelope'
-  noblank: true            # open link in current tab
 -
   type: rss
   icon: 'fas fa-rss'
   noblank: true
 
 # Uncomment and complete the url below to enable more contact options
 # -
+#   type: email
+#   icon: 'fas fa-envelope'
+#   noblank: true            # open link in current tab
+# -
 #   type: mastodon
 #   icon: 'fab fa-mastodon'   # icons powered by <https://fontawesome.com/>
 #   url:  ''                  # Fill with your mastodon account page

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

@@ -0,0 +1,17 @@
+---
+layout: post
+title: 'Hello World!'
+date: 2020-07-16 -0500
+category: 'General'
+tags: 'general'
+---
+
+Finally, I have a blog set up.
+
+Hello World
+
+I decided to use [Jekyll](https://jekyllrb.com/) and [GitHub Pages](https://pages.github.com/) to host this blog. It's very easy and mostly automated, and it allows me to focus on content, rather than the hosting and layout. I've created a simple theme for that reason.
+
+<!--more-->
+
+I definitely recommend checking out [**barryclark/jekyll-now**](https://github.com/barryclark/jekyll-now) to get started if you're interested in doing the same.

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

@@ -0,0 +1,85 @@
+---
+layout: post
+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']
+---
+
+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.
+
+<!--more-->
+
+## Some considerations
+
+Keep in mind, your build version numbers will need to be compliant with [normalized SEMVER2](https://github.com/NuGet/Home/wiki/SemVer-2.0.0-support#spec) to be valid for NPM.
+
+### 1) Adding node types to Angular
+
+In your `tsconfig.app.json` file, add `node` to the `types` array. If there is not a already `types` array, add it under `compilerOptions` in the json root.
+
+```json
+{
+  "compilerOptions": {
+    "types": ["node"]
+  }
+}
+```
+
+### 2) Adding environment variables
+
+Find your `environment` constant in `src/environments`. You should see two files, one for prod, `environment.prod.ts`, and one for not-prod, `environment.ts`. In production, I keep it simple and add the `appVersion` variable without any changes.
+
+```js
+export const environment = {
+  appVersion: require('../../package.json').version,
+  production: true,
+  base: 'area',
+};
+```
+
+In the non-production environment though, I like to add a dev tag.
+
+```js
+// comment
+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.
+
+### 3) Adding the version to an Angular component
+
+Likewise this is easier than it sounds. Now that the node types and version variable are available, they just need to be accessed and displayed somewhere in the app. I prefer to add this to the bootstrapped component, which is usually `AppComponent`. This best way I've found to do this is with a host binding.
+
+**Note**: _You do not need to specify `prod` vs `non-prod` in your environment import. When Angular builds, it will use the production environment if the `--prod` build flag is used._
+
+```js
+import { Component, HostBinding } from '@angular/core';
+import { environment } from 'src/environments/environment';
+
+@Component({
+  ...
+})
+export class AppComponent {
+  @HostBinding('attr.app-version') appVersionAttr = environment.appVersion;
+}
+```
+
+### 4) Adding `npm version` to your pipeline
+
+If your pipeline stack offers automatically created version numbers, just make sure they are compliant with [normalized SEMVER2](https://github.com/NuGet/Home/wiki/SemVer-2.0.0-support#spec). Once you have add a task in your pipeline to run the npm command
+
+```bash
+npm version $(build.buildNumber)
+```
+
+The build variable above is for [Azure Devops](https://docs.microsoft.com/en-us/azure/devops/?view=azure-devops) specifically. Your pipeline stack may differ.
+
+## Last Thoughts
+
+Now that you've added a version number, build, build, build and check then check your work. You should see an html attribute on whatever html element you added the host binding to. For me it looks like this:
+
+```html
+<app-root app-version="3.1.28-master"></app-root>
+```

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

@@ -0,0 +1,37 @@
+---
+layout: post
+title: 'Creating a super Outlook SPAM Rule'
+date: 2021-03-23 22:40:00 -0500
+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.
+
+<!--more-->
+
+## Notes
+
+So, I'll start off saying here my situation may be unique. I only care about email from people inside my organization. If that's not the case for you, this definitely won't work for you. I'll also say I have a lot of other rules that run ahead of this rule to pick up any external email that I might care about. Like notifications from Azure or external monitoring notifications. Those are important and have their own rules governing how they're handled.
+
+## Into the Clouds!
+
+These rules work best when created in the online version of the Outlook client. If they are created on a specific, local client, they will only run when that client is running. When created in the _cloud_ they will always run. My organization uses [Office 365](https://outlook.office365.com/mail/inbox) so I headed there.
+
+## Find your rules
+
+For me, the easiest way to pull up email rules is to click on the settings icon (gear/cog) in the top right. From there I click `View all Outlook settings` near the bottom of the panel that appears. This will pull up another menu. With `Mail` selected, I click `rules` from the options on the left. If you have other rules set up already, you should see them here.
+
+## SPAM be gone
+
+From here click `Add new rule`. A create rule screen will appear and you can start setting up the rule. I named my rule "Not from {organization} is Junk". Under condition choose `Apply to all messages`. This may seem wrong at first, but it will make more sense in a second.
+
+![Rules](/assets/img/outlook-spam-rules.png)
+
+Add the action to `Move to` the `Junk Email` folder, and for an added nicety, Add anohter action to set `Mark as read` too.
+
+Lastly, and most importantly, set the exception. The rules here can be tailored to meet your needs, but for me, `Sender address includes` and then my {@organization.com} did the trick.
+
+## Finally
+
+Now my inbox is much leaner. Occasionally I will check the junk folder just to see if I miseed anything, but so far I haven't.