Add untracked files

.atom-build.yml

@@ -0,0 +1,13 @@
+cmd: 'build-wrapper podman-run-wrapper --debug -m ephemeral -o "-it -p 4000:4000 -v /home/bryan/Documents/develop/www/blog.bryanroessler.com:/srv/jekyll -v /home/bryan/Documents/develop/www/blog.bryanroessler.com/vendor/bundle:/usr/local/bundle" -i jekyll/jekyll -n "jekyll-blog" "bundle exec jekyll serve --watch --drafts"'
+name: 'blog.bryanroessler.com--SERVE'
+targets:
+  blog.bryanroessler.com--BUNDLE-UPDATE:
+    cmd: 'build-wrapper podman-run-wrapper --debug -m ephemeral -o "-it -p 4000:4000 -v /home/bryan/Documents/develop/www/blog.bryanroessler.com:/srv/jekyll -v /home/bryan/Documents/develop/www/blog.bryanroessler.com/vendor/bundle:/usr/local/bundle" -i jekyll/jekyll -n "jekyll-blog" --selinuxfix "chmod a+w /srv/jekyll/Gemfile.lock && bundle update --all"'
+  landing.bryanroessler.com--SERVE:
+    cmd: 'build-wrapper podman-run-wrapper --debug -m ephemeral -o "-it -p 4000:4000 -v /home/bryan/Documents/develop/www/landing.bryanroessler.com:/srv/jekyll -v /home/bryan/Documents/develop/www/landing.bryanroessler.com/vendor/bundle:/usr/local/bundle" -i jekyll/jekyll -n "jekyll-landing" "bundle exec jekyll serve --watch --drafts"'
+  landing.bryanroessler.com--BUNDLE-UPDATE:
+    cmd: 'build-wrapper podman-run-wrapper --debug -m ephemeral -o "-it -p 4000:4000 -v /home/bryan/Documents/develop/www/landing.bryanroessler.com:/srv/jekyll -v /home/bryan/Documents/develop/www/landing.bryanroessler.com/vendor/bundle:/usr/local/bundle" -i jekyll/jekyll -n "jekyll-landing" --selinuxfix "chmod a+w /srv/jekyll/Gemfile.lock && bundle update --all"'
+  cv.bryanroessler.com--SERVE:
+    cmd: 'build-wrapper podman-run-wrapper --debug -m ephemeral -o "-it -p 4000:4000 -v /home/bryan/Documents/develop/www/cv.bryanroessler.com:/srv/jekyll -v /home/bryan/Documents/develop/www/cv.bryanroessler.com/vendor/bundle:/usr/local/bundle" -i jekyll/jekyll -n "jekyll-cv" "bundle exec jekyll serve --watch --drafts"'
+  cv.bryanroessler.com--BUNDLE-UPDATE:
+    cmd: 'build-wrapper podman-run-wrapper --debug -m ephemeral -o "-it -p 4000:4000 -v /home/bryan/Documents/develop/www/cv.bryanroessler.com:/srv/jekyll -v /home/bryan/Documents/develop/www/cv.bryanroessler.com/vendor/bundle:/usr/local/bundle" -i jekyll/jekyll -n "jekyll-cv" --selinuxfix "chmod a+w /srv/jekyll/Gemfile.lock && bundle update --all"'

.gitignore

@@ -0,0 +1,3 @@
+*.sublime*
+landing.jennakuzma.com/
+landing.jennakuzma.com.bak/

blog.bryanroessler.com/.github/FUNDING.yml

@@ -0,0 +1,3 @@
+# These are supported funding model platforms
+
+#github: daattali

blog.bryanroessler.com/.github/issue_template.md

@@ -0,0 +1,3 @@
+Thank you for submitting an issue!
+
+Please only submit bug reports or feature suggestions. Please do not submit support requests and general help questions in this forum.

blog.bryanroessler.com/.github/pull_request_template.md

@@ -0,0 +1,5 @@
+Please note that if you are trying to update **your** website, this is the wrong place to do so. Please carefully follow the Beautiful Jekyll instructions (found at https://github.com/daattali/beautiful-jekyll#readme) and make sure you submit changes to **your** version of the project.
+
+If your intention is to submit a Pull Request, please describe what your pull request achieves.
+
+Thank you!

blog.bryanroessler.com/.github/workflows/ci.yml

@@ -0,0 +1,26 @@
+name: Beautiful Jekyll CI
+on: [push, pull_request]
+jobs:
+  build:
+    name: Build Jekyll
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: '3.3'
+      - name: Install dependencies
+        run: bundle install && bundle exec appraisal install
+      - name: Setup Pages
+        id: configure-pages
+        uses: actions/configure-pages@v5
+      - name: Setup CI config
+        run: |
+          echo "---" > _config_ci.yml
+          echo "baseurl: ${{ steps.configure-pages.outputs.base_path }}" >> _config_ci.yml
+      - name: Build site
+        env:
+          JEKYLL_ENV: production
+        run: bundle exec appraisal jekyll build --future --config _config_ci.yml,_config.yml
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3

blog.bryanroessler.com/.gitignore

@@ -3,9 +3,15 @@ _site
 .sass-cache
 .vagrant
 .bundle
-vendor/bundle
+.jekyll-cache
+vendor
+_drafts
 
 # general
 .DS_Store
 Thumbs.db
 ehthumbs.db
+
+Gemfile.lock
+
+beautiful-jekyll-theme-*.gem

blog.bryanroessler.com/Appraisals

@@ -0,0 +1,6 @@
+appraise "jekyll-3" do
+  gem "jekyll", "3.9.4"
+end
+appraise "jekyll-4" do
+  gem "jekyll", "4.3.3"
+end

blog.bryanroessler.com/CHANGELOG.md

@@ -0,0 +1,248 @@
+## Unreleased version
+- BREAKING CHANGE: Allow changing the order of the social network links that appear in the footer (#1152)
+- BREAKING CHANGE: `google-scholar` social network link no longer requires the prefix `citations?user=`; if you previously set this parameter, it needs to be updated (#1189)
+- Added `mathjax` YAML parameter to allow support for MathJax, used to write LaTeX expressions (#195)
+- Added explicit support for favicons, you only need to add a `favicon.ico` file to the root directory
+- The footer of a page always sticks to the bottom, even on short pages (#576)
+- Added `author` YAML parameter to allow specifying the author(s) of a post (#1220)
+- Fixed bug where search results broke if a post title had a backslash (#1279)
+- Fixed bug where hovering over search results showed the text "{desc}" (#1156)
+- Added social network links for GitLab, Bluesky, Whatsapp, Untappd (#1168, #1218, #1299, #1307)
+- Support reddit social network link to either be a subreddit or a user (#1371)
+- Use CSS variables (#661)
+- Added instructions and example on how to fix image links in project sites (#1171)
+- Pagination buttons: use nicer arrows, and don't show text on small screens (#1221)
+- Updated Yelp URL format - if you previously used the `yelp` social network config parameter, you might need to update the config value (#1259)
+- Added `title-on-all-pages` config setting, that adds the website title to all page titles (#1272)
+- Change Twitter icon to X (#1193)
+- Upgraded font-awesome to 6.5.2 (#1330)
+
+## v6.0.1 (2023-06-08)
+
+This version has been in the works for a few years. It includes several new features that were highly requested, numerous bug fixes, new documentation, and aggresively encourages migrating from the old Google Universal Analytics to the new Analytics 4.
+
+#### Breaking changes
+
+- As of July 2023, Google Universal Analytics is going away and being replaced by Google Analytics 4. Beautiful Jekyll sites that still use the old analytics tag will show a warning to encourage them to move to Analytics 4 (#1096).
+- More control over RSS feed sharing: previously, an RSS feed was *always* generated, and if the config setting `rss-description` was set then there was an RSS icon in the footer. Now, an RSS feed is only generated when the config setting `rss-description` exists, and an RSS footer icon is only shown if `rss: true` is set in the `social-network-links` config settings.
+
+#### New parameters and settings
+
+- Added `navbar-var-length` config setting that allows the navigation menu to be the same length as the longest sub-menu, so that long words in the submenu are not cut off (#765) 
+- Added `post_search` config setting that creates a Search button in the navbar (#770)
+- Added `edit_page_button` config setting that adds a "Edit page" button to the footer (to edit the current page on GitHub) (#1004)
+- Added `footer-hover-col` config setting to customize the hover colour of links in the footer (#848)
+
+#### New features and improvements
+
+- Made the home page feed more accessible for screen readers (#950)
+- Added support for giscus comments (#886) and CommentBox (#960)
+- Added support for Cloudflare Analytics (#797)
+- Added Reddit in share options of posts (#815)
+
+#### Bug fixes
+
+- Fixed page titles, subtitles, and excerpts rendering correctly when there are special characeters in them (#856) 
+- Fixed bug where navbar secondary level dropdown items didn't inherit the same colour as the primary navbar links
+- Fixed bug where the navbar "burger" collapsed button didn't always revert back to a light colour
+- Fixed bug where using an image as a navbar title did not render in GitHub Project pages that did not have a custom domain
+- Fixed bug where image thumbnails on the feed page were always forced into a square rather than maintaining a proper image aspect ratio
+- Fixed bug where special characters in the title led to broken share tags (#744)
+- Fixed bug where staticman didn't work jQuery slim version is used (#766)
+- Fixed very long strings to wrap around the next line rather than go off-screen (#787)
+
+#### Small changes
+
+- Updated staticman from using v2 (public servers) to v3 (private servers) due to the public servers becoming obsolete (#775)
+- Added social network links for Patreon, Medium, Itch.io, Discord, Kaggle, Hackerrank (#783, #788, #907, #961, #978)
+- Slightly reworked margins and position for avatar image to resolve an alignment issue on Safari
+- Changed the width at which the navbar collapses to a higher threshold because most modern non-mobile browsers are >1000px
+
+
+## v5.0.0 (2020-09-15)
+
+One of the major changes in this version is that a lot of time was spent on rethinking the entire SEO and social media sharing model (how a page looks on eg. Google, Twitter, Facebok). It was redesigned to be more simple and customizable. The new documentation has a section dedicated to SEO and social media sharing of a page. Unfortunately some changes that are not backwards-compatible had to be made.
+
+#### Breaking changes
+
+- Renamed `description` YAML parameter to `share-description` to be more clear
+- Renamed `description` config setting to `rss-description` since it was only used in RSS (the FAQ explains the difference between YAML parameters and config settings if you're confused)
+- Removed YAML parameter `use-site-title` (you can now specify the exact title using `share-title`)
+- Removed undocumented YAML parameters `meta-title` and `meta-description`
+- Removed `link-tags` config setting because it wasn't necessary. If you use tags, there will now always be a tags page created; if you don't use tags there won't be a tags page.
+- The YAML parameter `show-avatar` is now true by default. This has always been the case for GitHub Pages users, but not for `remote_theme` users. For consistency, it's now the default for everyone. (#715)
+
+#### New parameters and settings
+
+- Added `full-width` YAML parameter to allow having full-width pages
+- Added `feed_show_excerpt` config setting to show/hide the post excerpts on the feed page
+- Added `feed_show_tags` config setting to show/hide the list of tags on post previews on the feed page
+- Added `share-title` YAML parameter to give control over the search engine/social media title
+- Added `last-updated` YAML parameter to show a "Last Updated on" date for blog posts
+- Added `before-content` and `after-content` YAML parameters that allow you to add some common HTML before the main content of a page (below the title) or after the main content (above the footer). Works in a similar way to `footer-extra`.
+- Added `head-extra` YAML parameter which is similar to `footer-extra` but is used to include custom HTML code in a page's `<head>` tag
+- Added `site-js` config setting to provide JavaScript files that are used on all pages in the site
+
+#### New features and improvements
+
+- Improved the `footer-extra` YAML parameter to support multiple files instead of only a single file
+- Added automatic navbar color detection (#702)
+- When `nav-short` is turned on, the avatar will also be shorter
+- Changed navbar and footer background colour to be slightly darker, for better contrast with the default white page background for accessibility reasons
+- Changed the behaviour of `site-css` to include site-wide CSS file **before** instead of after page-specific files
+- Renamed internal css/js files from "main" to "beautifuljekyll" to make it easier for users to troubleshoot
+- Added alt text to all images for better accessibility
+- Made thumbnail images square instead of circles, as users reported that circles cut off important parts of images
+
+#### Bug fixes
+
+- Fixed rendering issues with `nav-short` parameter that caused the body of the page to start too low
+- Fixed some CSS styles that broke during the bootstrap 4 migration (#716)
+
+#### Library upgrades
+
+- Upgraded kramdown to version 2.3.0 to fix security issues
+- Upgraded jQuery to version 3.5.1 to fix a couple security vulnerabilities with the previous version
+
+## v4.1.0 (2020-08-08)
+
+- Added Open Graph `site_name` meta field to pages automatically
+- Added `text-col` config setting  for main text color (#694)
+- Added `keywords` config setting to set the meta keywords on all pages (for SEO purposes) (#691)
+- Added `mobile-theme-col` config setting to allow a mobile theme colour (#692)
+- Added `site-css` config setting in the config file to provide CSS files that are used on all pages in the site (#695)
+- Added YAML parameter `description`: creates the meta description on a page, intended to provide a brief description of the page for search engines and when the page is shared (#690)
+
+## v4.0.1 (2020-07-13)
+
+- Fixed staticman comments UI that was broken since the migration to bootstrap 4
+
+## v4.0.0 (2020-07-12)
+
+- **BREAKING CHANGE** Replace `image` YAML parameter with `thumbnail-img` to be more clear
+- **MAJOR BEHAVIOUR CHANGE** Don't use the thumbnail as the avatar image
+- Cover image will automatically be used as thumbnail if none is provided
+- Image to share on social media will use the cover image or thumbnail if none is provided
+- All images (social media share, thumbnail, cover) can use either relative or absoluate paths.
+- Fixed issue where if a dropdown menu was the last item in the menu bar, it did not have a proper margin on the right
+- Added social network links: Mastodon (#646), Google Scholar, ORCID (#670)
+- Added support for sharing pages on new social network: VK (#657)
+- Use Open Graph type 'article' for blog posts (#669)
+- Use Twitter's large sumary card (large image) when there is a cover image, thumbnail image, or share image specified (#668)
+- Made post images in the feed page smaller on smaller devices
+- Fixed jQuery version in staticman (#671)
+
+## v3.0.0 (2020-05-07)
+
+- **BREAKING CHANGE** Upgraded from Bootstrap 3.3.2 to 4.4.1. This involved a major rewrite of most components. This shouldn't affect any users unless you have custom HTML/CSS code which the new Bootstrap could have broken.
+- **BREAKING CHANGE** Renamed `bigimg` YAML parameter to `cover-img`
+- **BREAKING CHANGE** Removed `googlefonts` YAML parameter since googlefonts are just CSS so they can be loaded via `ext-css`
+- **BREAKING CHANGE** Upgraded from jQuery 1.11.2 to 3.4.2. This should not affect most people
+- Added `navbar-border-col` setting in the config file
+- Added accessibility features where possible
+- Made the theme completely responsive by rewriting all CSS to use 'rem' instead of 'px'
+- Rewrote and simplified some JavaScript code to use CSS or Bootstrap alternatives that weren't available in 2015
+- Removed most of the sample posts so that users only have two sample posts to learn from
+- Improvements to the README instructions
+
+## v2.3.0 (2020-04-29)
+
+- Added YAML parameter `footer-extra` for including custom content in the footer
+- Fixed issue: linking to a specific part of a page resulted in scrolling too far (#69)
+- Added YAML parameter `nav-short` to have navbar permanently collapsed
+- Added social network link: Calendly
+- Fixed bug where RSS link in footer was showing even when turned off
+
+## v2.2.0 (2020-04-27)
+
+- Added social network link: Telegram (#625) (thanks @mashed-potatoes)
+- Moved the demo site to an independent URL: https://beautifuljekyll.com
+- Major documentation overhaul and cleanup of old files
+- Fixed a few bugs from the remote_theme migration
+
+## v2.0.0 (2020-04-26)
+
+- Beautiful-Jekyll v2.0.0 available as an official Ruby gem
+- Beautifull-Jekyll now supports the `remote_theme` config (#339) (thanks @gpotter2 and @skalee)
+- Consolidated the demo site, the ruby gem, and the master branch into one
+- Added a `home` layout and used it in the index page
+- Added readtime support for the post header (#622) (thanks @MutMatt and @rubyreads)
+- Removed the dependency on `_data` folder since it doesn't get copied when using `remote_theme` (#614)
+- Added support for configuring lang attribute on `html` tag (#608) (thanks @skalee)
+- Added ability to disable round logo (thanks @gpotter2)
+- Added support for Utterances comments (#596) (thanks @colynn)
+- Removed 'just-comments' as it's getting killed at the end of the year
+- Upgraded font-awesome to 5.12.1 (#587) (thanks @cketti)
+
+## Prior to 2020
+
+**2018-12-24** Add support for Staticman comments (#440) (thanks @VincentTam)
+
+**2018-10-19** Move Google Analytics to the head (#419) (thanks @jpvicari)
+
+**2018-06-08** Add support for Facebook comments (#350) (thanks @npes87184)
+
+**2018-02-22** Automatically generate sitemap (#323) (thanks @JosemyDuarte)
+
+**2018-01-18** Add clickable tags to each post and a tags index page, works for GitHub sites (#307) (thanks @OCram85)
+
+**2018-01-14** Redo Dockerfile (#302) (thanks @jennydaman)
+
+**2018-01-06** More color personalization options (#297 and #299) (thanks @jennydaman)
+
+**2018-01-05** Abstract the social networks logic (thanks @OCram85)
+
+**2018-01-03** Avatar image no longer causes a ghost click (thanks @alefi87)
+
+**2017-10-16** Add GitHub buttons to posts (#265) (thanks @yonicd)
+
+**2017-09-04** Ability to change colour/image of navbar/footer/body
+
+**2017-08-17** Add support for notification, error, and warning boxes in markdown (#227) (thanks @OCram85)
+
+**2017-08-12** Add social buttons for twitch, yelp, and steam (#234) (thanks @TheRealBenForce)
+
+**2017-03-30** Make the footer contact links friendly for screen readers (thanks @eugenius1)
+
+**2017-03-30** Started a CHANGELOG file (thanks @eugenius1)
+
+**2017-01-28** Add Subresource Integrity (SRI) support (#164) (thanks @tony-ho)
+
+**2017-01-09** Add Google Tag Manager Integration (#157) (thanks @csarigoz)
+
+**2017-01-06** Add options to configure HTML document title (#154) (thanks @tony-ho)
+
+**2016-12-25** Allow dynamic images on each blog post (#143) (thanks @bbritten)
+
+**2016-12-15** Support `title-img` config param to have image in the navbar instead of text
+
+**2016-12-08** Add support for phone numbers in footer; fix #136
+
+**2016-12-06** Update gemfile (#134) (thanks @stephentuso)
+
+**2016-10-09** Add Docker deployment (#114) (thanks @mangar)
+
+**2016-08-06** Add social share buttons for posts (thanks @rtlee9)
+
+**2016-07-29** Add CSS styling to code chunks
+
+**2016-07-27** Add clickable tags that lead to a tag page (doesn't work for GitHub hosted sites) (thanks @epwalsh)
+
+**2016-07-21** Add support for twitter cards (sharing on Twitter will be better); fixes #70
+
+**2016-03-18** Support full-width images in page headers; fixes #37
+
+**2016-03-18** Support menus in navigation bar
+
+**2016-02-07** Avatar is now conditional (thanks @hristoyankov)
+
+**2016-02-02** Migrate (forced to...) to jekyll 3
+
+**2016-01-22** Make sure not to include JQuery twice, fixes #29
+
+**2015-11-19** Support external links in navigation bar; fixes #3
+
+... Many small changes because the site was in its infancy
+
+**2015-03-12** Beautiful Jekyll version 0.0000001 is released!
+

blog.bryanroessler.com/Dockerfile

@@ -1,8 +1,8 @@
 FROM jekyll/jekyll
 
-COPY Gemfile .
-COPY Gemfile.lock .
+COPY --chown=jekyll:jekyll Gemfile .
+#COPY --chown=jekyll:jekyll Gemfile.lock .
 
-RUN bundle install --quiet --clean
+RUN bundle install --clean
 
 CMD ["jekyll", "serve"]

blog.bryanroessler.com/Gemfile

@@ -1,7 +1,5 @@
-source 'https://rubygems.org'
+# frozen_string_literal: true
 
-gem "github-pages", '193', group: :jekyll_plugins
+source "https://rubygems.org"
 
-# enable tzinfo-data for local build
-# gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw]
-gem 'jekyll-paginate'
+gemspec

blog.bryanroessler.com/Gemfile.lock

@@ -1,254 +1,172 @@
+PATH
+  remote: .
+  specs:
+    beautiful-jekyll-theme (6.0.1)
+      jekyll (>= 3.9.3)
+      jekyll-paginate (~> 1.1)
+      jekyll-sitemap (~> 1.4)
+      kramdown (~> 2.3)
+      kramdown-parser-gfm (~> 1.1)
+      webrick (~> 1.8)
+
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (4.2.10)
-      i18n (~> 0.7)
-      minitest (~> 5.1)
-      thread_safe (~> 0.3, >= 0.3.4)
-      tzinfo (~> 1.1)
-    addressable (2.5.2)
-      public_suffix (>= 2.0.2, < 4.0)
-    coffee-script (2.4.1)
-      coffee-script-source
-      execjs
-    coffee-script-source (1.11.1)
+    addressable (2.8.7)
+      public_suffix (>= 2.0.2, < 7.0)
+    appraisal (2.5.0)
+      bundler
+      rake
+      thor (>= 0.14.0)
     colorator (1.1.0)
-    commonmarker (0.17.13)
-      ruby-enum (~> 0.5)
-    concurrent-ruby (1.1.3)
-    dnsruby (1.61.2)
-      addressable (~> 2.5)
-    em-websocket (0.5.1)
+    concurrent-ruby (1.3.4)
+    em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
-      http_parser.rb (~> 0.6.0)
-    ethon (0.11.0)
-      ffi (>= 1.3.0)
+      http_parser.rb (~> 0)
     eventmachine (1.2.7)
-    eventmachine (1.2.7-x64-mingw32)
-    execjs (2.7.0)
-    faraday (0.15.3)
-      multipart-post (>= 1.2, < 3)
-    ffi (1.9.25)
-    ffi (1.9.25-x64-mingw32)
+    ffi (1.17.0)
+    ffi (1.17.0-aarch64-linux-gnu)
+    ffi (1.17.0-aarch64-linux-musl)
+    ffi (1.17.0-arm-linux-gnu)
+    ffi (1.17.0-arm-linux-musl)
+    ffi (1.17.0-arm64-darwin)
+    ffi (1.17.0-x86-linux-gnu)
+    ffi (1.17.0-x86-linux-musl)
+    ffi (1.17.0-x86_64-darwin)
+    ffi (1.17.0-x86_64-linux-gnu)
+    ffi (1.17.0-x86_64-linux-musl)
     forwardable-extended (2.6.0)
-    gemoji (3.0.0)
-    github-pages (193)
-      activesupport (= 4.2.10)
-      github-pages-health-check (= 1.8.1)
-      jekyll (= 3.7.4)
-      jekyll-avatar (= 0.6.0)
-      jekyll-coffeescript (= 1.1.1)
-      jekyll-commonmark-ghpages (= 0.1.5)
-      jekyll-default-layout (= 0.1.4)
-      jekyll-feed (= 0.11.0)
-      jekyll-gist (= 1.5.0)
-      jekyll-github-metadata (= 2.9.4)
-      jekyll-mentions (= 1.4.1)
-      jekyll-optional-front-matter (= 0.3.0)
-      jekyll-paginate (= 1.1.0)
-      jekyll-readme-index (= 0.2.0)
-      jekyll-redirect-from (= 0.14.0)
-      jekyll-relative-links (= 0.5.3)
-      jekyll-remote-theme (= 0.3.1)
-      jekyll-sass-converter (= 1.5.2)
-      jekyll-seo-tag (= 2.5.0)
-      jekyll-sitemap (= 1.2.0)
-      jekyll-swiss (= 0.4.0)
-      jekyll-theme-architect (= 0.1.1)
-      jekyll-theme-cayman (= 0.1.1)
-      jekyll-theme-dinky (= 0.1.1)
-      jekyll-theme-hacker (= 0.1.1)
-      jekyll-theme-leap-day (= 0.1.1)
-      jekyll-theme-merlot (= 0.1.1)
-      jekyll-theme-midnight (= 0.1.1)
-      jekyll-theme-minimal (= 0.1.1)
-      jekyll-theme-modernist (= 0.1.1)
-      jekyll-theme-primer (= 0.5.3)
-      jekyll-theme-slate (= 0.1.1)
-      jekyll-theme-tactile (= 0.1.1)
-      jekyll-theme-time-machine (= 0.1.1)
-      jekyll-titles-from-headings (= 0.5.1)
-      jemoji (= 0.10.1)
-      kramdown (= 1.17.0)
-      liquid (= 4.0.0)
-      listen (= 3.1.5)
-      mercenary (~> 0.3)
-      minima (= 2.5.0)
-      nokogiri (>= 1.8.2, < 2.0)
-      rouge (= 2.2.1)
-      terminal-table (~> 1.4)
-    github-pages-health-check (1.8.1)
-      addressable (~> 2.3)
-      dnsruby (~> 1.60)
-      octokit (~> 4.0)
-      public_suffix (~> 2.0)
-      typhoeus (~> 1.3)
-    html-pipeline (2.9.1)
-      activesupport (>= 2)
-      nokogiri (>= 1.4)
-    http_parser.rb (0.6.0)
-    i18n (0.9.5)
+    google-protobuf (3.25.5)
+    google-protobuf (3.25.5-aarch64-linux)
+    google-protobuf (3.25.5-arm64-darwin)
+    google-protobuf (3.25.5-x86-linux)
+    google-protobuf (3.25.5-x86_64-darwin)
+    google-protobuf (3.25.5-x86_64-linux)
+    http_parser.rb (0.8.0)
+    i18n (1.14.6)
       concurrent-ruby (~> 1.0)
-    jekyll (3.7.4)
+    jekyll (4.3.4)
       addressable (~> 2.4)
       colorator (~> 1.0)
       em-websocket (~> 0.5)
-      i18n (~> 0.7)
-      jekyll-sass-converter (~> 1.0)
+      i18n (~> 1.0)
+      jekyll-sass-converter (>= 2.0, < 4.0)
       jekyll-watch (~> 2.0)
-      kramdown (~> 1.14)
+      kramdown (~> 2.3, >= 2.3.1)
+      kramdown-parser-gfm (~> 1.0)
       liquid (~> 4.0)
-      mercenary (~> 0.3.3)
+      mercenary (>= 0.3.6, < 0.5)
       pathutil (~> 0.9)
-      rouge (>= 1.7, < 4)
+      rouge (>= 3.0, < 5.0)
       safe_yaml (~> 1.0)
-    jekyll-avatar (0.6.0)
-      jekyll (~> 3.0)
-    jekyll-coffeescript (1.1.1)
-      coffee-script (~> 2.2)
-      coffee-script-source (~> 1.11.1)
-    jekyll-commonmark (1.2.0)
-      commonmarker (~> 0.14)
-      jekyll (>= 3.0, < 4.0)
-    jekyll-commonmark-ghpages (0.1.5)
-      commonmarker (~> 0.17.6)
-      jekyll-commonmark (~> 1)
-      rouge (~> 2)
-    jekyll-default-layout (0.1.4)
-      jekyll (~> 3.0)
-    jekyll-feed (0.11.0)
-      jekyll (~> 3.3)
-    jekyll-gist (1.5.0)
-      octokit (~> 4.2)
-    jekyll-github-metadata (2.9.4)
-      jekyll (~> 3.1)
-      octokit (~> 4.0, != 4.4.0)
-    jekyll-mentions (1.4.1)
-      html-pipeline (~> 2.3)
-      jekyll (~> 3.0)
-    jekyll-optional-front-matter (0.3.0)
-      jekyll (~> 3.0)
+      terminal-table (>= 1.8, < 4.0)
+      webrick (~> 1.7)
     jekyll-paginate (1.1.0)
-    jekyll-readme-index (0.2.0)
-      jekyll (~> 3.0)
-    jekyll-redirect-from (0.14.0)
-      jekyll (~> 3.3)
-    jekyll-relative-links (0.5.3)
-      jekyll (~> 3.3)
-    jekyll-remote-theme (0.3.1)
-      jekyll (~> 3.5)
-      rubyzip (>= 1.2.1, < 3.0)
-    jekyll-sass-converter (1.5.2)
-      sass (~> 3.4)
-    jekyll-seo-tag (2.5.0)
-      jekyll (~> 3.3)
-    jekyll-sitemap (1.2.0)
-      jekyll (~> 3.3)
-    jekyll-swiss (0.4.0)
-    jekyll-theme-architect (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-cayman (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-dinky (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-hacker (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-leap-day (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-merlot (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-midnight (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-minimal (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-modernist (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-primer (0.5.3)
-      jekyll (~> 3.5)
-      jekyll-github-metadata (~> 2.9)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-slate (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-tactile (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-time-machine (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-titles-from-headings (0.5.1)
-      jekyll (~> 3.3)
-    jekyll-watch (2.1.2)
+    jekyll-sass-converter (3.0.0)
+      sass-embedded (~> 1.54)
+    jekyll-sitemap (1.4.0)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-watch (2.2.1)
       listen (~> 3.0)
-    jemoji (0.10.1)
-      gemoji (~> 3.0)
-      html-pipeline (~> 2.2)
-      jekyll (~> 3.0)
-    kramdown (1.17.0)
-    liquid (4.0.0)
-    listen (3.1.5)
-      rb-fsevent (~> 0.9, >= 0.9.4)
-      rb-inotify (~> 0.9, >= 0.9.7)
-      ruby_dep (~> 1.2)
-    mercenary (0.3.6)
-    mini_portile2 (2.3.0)
-    minima (2.5.0)
-      jekyll (~> 3.5)
-      jekyll-feed (~> 0.9)
-      jekyll-seo-tag (~> 2.1)
-    minitest (5.11.3)
-    multipart-post (2.0.0)
-    nokogiri (1.8.5)
-      mini_portile2 (~> 2.3.0)
-    nokogiri (1.8.5-x64-mingw32)
-      mini_portile2 (~> 2.3.0)
-    octokit (4.13.0)
-      sawyer (~> 0.8.0, >= 0.5.3)
+    kramdown (2.5.1)
+      rexml (>= 3.3.9)
+    kramdown-parser-gfm (1.1.0)
+      kramdown (~> 2.0)
+    liquid (4.0.4)
+    listen (3.9.0)
+      rb-fsevent (~> 0.10, >= 0.10.3)
+      rb-inotify (~> 0.9, >= 0.9.10)
+    mercenary (0.4.0)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    public_suffix (2.0.5)
-    rb-fsevent (0.10.3)
-    rb-inotify (0.9.10)
-      ffi (>= 0.5.0, < 2)
-    rouge (2.2.1)
-    ruby-enum (0.7.2)
-      i18n
-    ruby_dep (1.5.0)
-    rubyzip (1.2.2)
-    safe_yaml (1.0.4)
-    sass (3.7.2)
-      sass-listen (~> 4.0.0)
-    sass-listen (4.0.0)
-      rb-fsevent (~> 0.9, >= 0.9.4)
-      rb-inotify (~> 0.9, >= 0.9.7)
-    sawyer (0.8.1)
-      addressable (>= 2.3.5, < 2.6)
-      faraday (~> 0.8, < 1.0)
-    terminal-table (1.8.0)
-      unicode-display_width (~> 1.1, >= 1.1.1)
-    thread_safe (0.3.6)
-    typhoeus (1.3.1)
-      ethon (>= 0.9.0)
-    tzinfo (1.2.5)
-      thread_safe (~> 0.1)
-    unicode-display_width (1.4.0)
+    public_suffix (6.0.1)
+    rake (12.3.3)
+    rb-fsevent (0.11.2)
+    rb-inotify (0.11.1)
+      ffi (~> 1.0)
+    rexml (3.3.9)
+    rouge (4.5.1)
+    safe_yaml (1.0.5)
+    sass-embedded (1.77.5-aarch64-linux-android)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-aarch64-linux-gnu)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-aarch64-linux-musl)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-aarch64-mingw-ucrt)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-arm-linux-androideabi)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-arm-linux-gnueabihf)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-arm-linux-musleabihf)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-arm64-darwin)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-riscv64-linux-android)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-riscv64-linux-gnu)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-riscv64-linux-musl)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-cygwin)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-linux-android)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-linux-gnu)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-linux-musl)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-mingw-ucrt)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-cygwin)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-darwin)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-linux-android)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-linux-gnu)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-linux-musl)
+      google-protobuf (>= 3.25, < 5.0)
+    terminal-table (3.0.2)
+      unicode-display_width (>= 1.1.1, < 3)
+    thor (1.3.2)
+    unicode-display_width (2.6.0)
+    webrick (1.9.1)
 
 PLATFORMS
-  ruby
-  x64-mingw32
+  aarch64-linux
+  aarch64-linux-android
+  aarch64-linux-gnu
+  aarch64-linux-musl
+  aarch64-mingw-ucrt
+  arm-linux-androideabi
+  arm-linux-gnu
+  arm-linux-gnueabihf
+  arm-linux-musl
+  arm-linux-musleabihf
+  arm64-darwin
+  riscv64-linux-android
+  riscv64-linux-gnu
+  riscv64-linux-musl
+  x86-cygwin
+  x86-linux
+  x86-linux-android
+  x86-linux-gnu
+  x86-linux-musl
+  x86-mingw-ucrt
+  x86_64-cygwin
+  x86_64-darwin
+  x86_64-linux-android
+  x86_64-linux-gnu
+  x86_64-linux-musl
 
 DEPENDENCIES
-  github-pages (= 193)
-  jekyll-paginate
+  appraisal (~> 2.5)
+  beautiful-jekyll-theme!
+  bundler (>= 1.16)
+  rake (~> 12.0)
 
 BUNDLED WITH
-   1.16.2
+   2.5.22

blog.bryanroessler.com/LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2016 Dean Attali
+Copyright (c) 2015-2018 Dean Attali
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -19,3 +19,12 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
+
+
+
+staticman integration
+=================================================================================
+
+The MIT License (MIT)
+
+Copyright (c) 2013-2018 Michael Rose

blog.bryanroessler.com/README.md

@@ -0,0 +1,325 @@
+# Beautiful Jekyll
+
+[![Donate](https://img.shields.io/badge/Donate-PayPal-green.svg)](https://www.paypal.me/daattali/20)
+[![Gem Version](https://badge.fury.io/rb/beautiful-jekyll-theme.svg)](https://badge.fury.io/rb/beautiful-jekyll-theme)
+
+> *Copyright 2019 [Dean Attali](https://deanattali.com)*
+
+**Beautiful Jekyll** is a ready-to-use template to help you create an awesome website quickly. Perfect for personal sites, blogs, or simple project websites.  [Check out a demo](https://deanattali.com/beautiful-jekyll) of what you'll get after just two minutes.  You can also look at [my personal website](https://deanattali.com) to see it in use, or see examples of websites other people created using this theme [here](#showcased-users-success-stories).
+
+**If you enjoy this theme, please consider [supporting me](https://www.paypal.me/daattali/20) for developing and maintaining this template.**
+
+<p align="center">
+  <a href="https://www.paypal.me/daattali">
+    <img src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" />
+  </a>
+</p>
+
+### Table of contents
+
+- [Prerequisites](#prerequisites)
+- [Build your website in 3 steps](#build-your-website-in-3-steps)
+- [Add your own content](#add-your-own-content)
+- [Last important thing: YAML front matter ("parameters" for a page)](#last-important-thing-yaml-front-matter-parameters-for-a-page)
+- [Features](#features)
+- [Creating a User Page vs a Project Page](#creating-a-user-page-vs-a-project-page)
+- [Showcased users (success stories!)](#showcased-users-success-stories)
+- [Advanced: local development](#advanced-local-development-using-docker)
+- [FAQ and support](#faq-and-support)
+- [Credits and contributions](#credits)
+
+## Prerequisites
+
+- You need to have a GitHub account. If you don't have one, [sign up here](https://github.com/join) - it takes one minute. This is where your website will live - if you sign up with username `johnsmith` then your website will be `https://johnsmith.github.io`.
+- It would be helpful to understand what Markdown is and how to write it. Markdown is just a way to take a piece of text and format it to look a little nicer.  For example, this whole instruction set that you're reading is written in markdown - it's just text with some words being bold/larger/italicized/etc. I recommend taking 5 minutes to learn markdown [with this amazingly easy yet useful tutorial](https://markdowntutorial.com/).
+
+## Build your website in 3 steps
+
+Getting started is *literally* as easy as 1-2-3 :smile:
+Scroll down to see the steps involved, but here is a 40-second video just as a reference as you work through the steps.
+
+![Installation steps](img/install-steps.gif)
+
+### 1. Fork this repository
+
+(Assuming you are on this page and logged into GitHub) Fork this repository by clicking the *Fork* button on the top right corner. Forking means that you now copied this whole project and all the files into your account.
+
+### 2. Rename the repository to `<yourusername>.github.io`
+
+This will create a GitHub User page ready with the **Beautiful Jekyll** template that will be available at `https://<yourusername>.github.io` within a couple minutes.  To do this, click on *Settings* at the top (the cog icon) and there you'll have an option to rename.
+
+### 3. Customize your website settings
+
+Edit the `_config.yml` file to change all the settings to reflect your site. To edit the file, click on it and then click on the pencil icon (watch the video tutorial above if you're confused).  The settings in the file are fairly self-explanatory and I added comments inside the file to help you further. Any line that begins with a pound sign (`#`) is a comment, and the rest of the lines are actual settings.
+
+Another way to edit the config file (or any other file) is to use [prose.io](https://prose.io/), which is just a simple interface to allow you to more intuitively edit files or add new files to your project.
+
+After you save your changes to the config file (by clicking on *Commit changes* as the video tutorial shows), your website should be ready in a minute or two at `https://<yourusername>.github.io`. Every time you make a change to any file, your website will get rebuilt and should be updated in about a minute or so.
+
+You can now visit your shiny new website, which will be seeded with several sample blog posts and a couple other pages. Your website is at `https://<yourusername>.github.io` (replace `<yourusername>` with your user name). Do not add `www` to the URL - it will not work!
+
+**Note:** The video above goes through the setup for a user with username `daattalitest`. I only edited one setting in the `_config.yml` file in the video, but **you should actually go through the rest of the settings as well. Don't be lazy, go through all the settings :)**
+
+## Add your own content
+
+To add pages to your site, you can either write a markdown file (`.md`) or you can write an HTML file directly.  It is much easier to write markdown than HTML, so I suggest you do that (use the [tutorial I mentioned above](https://markdowntutorial.com/) if you need to learn markdown). You can look at some files on this site to get an idea of how to write markdown. To look at existing files, click on any file that ends in `.md`, for example [`aboutme.md`](./aboutme.md). On the next page you can see some nicely formatted text (there is a word in bold, a link, bullet points), and if you click on the pencil icon to edit the file, you will see the markdown that generated the pretty text. Very easy!
+
+In contrast, look at [`index.html`](./index.html). That's how your write HTML - not as pretty. So stick with markdown if you don't know HTML.
+
+Any file that you add inside the [`_posts`](./_posts) directory will be treated as a blog entry.  You can look at the existing files there to get an idea of how to write blog posts.  After you successfully add your own post, you can delete the existing files inside [`_posts`](./_posts) to remove the sample posts, as those are just demo posts to help you learn.
+
+As mentioned previously, you can use [prose.io](https://prose.io/) to add or edit files instead of doing it directly on GitHub, it can be a little easier that way.
+
+## Last important thing: YAML front matter ("parameters" for a page)
+
+In order to have your new pages use this template and not just be plain pages, you need to add [YAML front matter](https://jekyllrb.com/docs/front-matter/) to the top of each page. This is where you'll give each page some parameters that I made available, such as a title and subtitle. I'll go into more detail about what parameters are available later. If you don't want to use any parameters on your new page (this also means having no title), then use the empty YAML front matter:
+
+```
+---
+---
+```
+
+If you want to use any parameters, write them between the two lines. For example, you can have this at the top of a page:
+
+```
+---
+title: Contact me
+subtitle: Here you'll find all the ways to get in touch with me
+---
+```
+
+You can look at the top of [`aboutme.md`](./aboutme.md) or [`index.html`](./index.html) as more examples.
+
+**Important takeaway: ALWAYS add the YAML front matter, which is two lines with three dashes, to EVERY page. If you have any parameters, they go between the two lines.**    
+If you don't include YAML then your file will not use the template.
+
+## Features
+
+### Mobile-first
+**Beautiful Jekyll** is designed to look great on both large-screen and small-screen (mobile) devices. Load up your site on your phone or your gigantic iMac, and the site will work well on both, though it will look slightly different.
+
+### Customizable
+
+Many personalization settings in `_config.yml`, such as setting your name and site's description, changing the background colour/image, setting your avatar to add a little image in the navigation bar, customizing the links in the menus, customizing what social media links to show in the footer, etc.
+
+### Allowing users to leave comments
+
+If you want to enable comments on your site, Beautiful Jekyll supports either the [Disqus](https://disqus.com/) comments plugin, [Facebook](https://developers.facebook.com/docs/plugins/comments) comments, [Staticman](https://staticman.net) or [JustComments](https://just-comments.com). If any of these are set in the configuration file, then all blog posts will have comments turned on by default. To turn off comments on a particular blog post, add `comments: false` to the YAML front matter. If you want to add comments on the bottom of a non-blog page, add `comments: true` to the YAML front matter.
+
+#### Disqus comments
+
+To use Disqus, simply sign up to [Disqus](https://disqus.com/) and add your Disqus shortname to the `disqus` parameter in the `_config.yml` file.
+
+#### Facebook comments
+
+To use Facebook comments, create a Facebook app using [Facebook developers](https://developers.facebook.com/docs/apps/register), and add the Facebook App ID to the `fb_comment_id` parameter in `_config.yml`.
+
+#### Staticman comments
+
+To use Staticman, you first need to invite `staticmanlab` as a collaborator to your repository (by going to your repository **Settings** page, navigate to the **Collaborators** tab, and add the username `staticmanlab`), and then accept the invitation by going to `https://staticman3.herokuapp.com/v3/connect/github/<username>/<repo-name>`. Lastly, fill in the `staticman` parameters in the Staticman section of `_config.yml`. You may also choose a different Staticman instance other than `staticmanlab`.
+
+Optional: You may want to configure a webhook to prevent old inactive branches (representing approved comments) from stacking up.  You can refer to [Staticman's documentation](https://staticman.net/docs/webhooks) for details.  Make sure to input the **Payload URL** according to your chosen `endpoint`.  For example, the default `endpoint` is `https://staticman3.herokuapp.com/v3/entry/github/`, so the corresponding **Payload URL** should be `https://staticman3.herokuapp.com/v1/webhook`.
+
+#### JustComments
+
+To use JustComments you first need to have an account. After you just need to copy the API key to the `just-comments` property in `_config.yml` file.
+
+### Adding Google Analytics to track page views
+
+Beautiful Jekyll lets you easily add Google Analytics to all your pages. This will let you track all sorts of information about visits to your website, such as how many times each page is viewed and where (geographically) your users come from.  To add Google Analytics, simply sign up to [Google Analytics](https://www.google.com/analytics/) to obtain your Google Tracking ID, and add this tracking ID to the `google_analytics` parameter in `_config.yml`.
+
+### Sharing blog posts on social media
+
+By default, all blog posts will have buttons at the bottom of the post to allow people to share the current page on Twitter/Facebook/LinkedIn.  You can choose to enable/disable specific social media websites in the `_config.yml` file. You can also turn off the social media buttons on specific blog posts using `social-share: false` in the YAML front matter.
+
+### RSS feed
+
+Beautiful Jekyll automatically generates a simple RSS feed of your blog posts, to allow others to subscribe to your posts.  If you want to add a link to your RSS feed in the footer of every page, find the `rss: false` line in `_config.yml` and change it to `rss: true`.
+
+### Page types
+
+- **post** - To write a blog post, add a markdown or HTML file in the `_posts` folder. As long as you give it YAML front matter (the two lines of three dashes), it will automatically be rendered like a blog post. Look at the existing blog post files to see examples of how to use YAML parameters in blog posts.
+- **page** - Any page outside the `_posts` folder that uses YAML front matter will have a very similar style to blog posts.
+- **minimal** - If you want to create a page with minimal styling (ie. without the bulky navigation bar and footer), assign `layout: minimal` to the YAML front matter.
+- If you want to completely bypass the template engine and just write your own HTML page, simply omit the YAML front matter. Only do this if you know how to write HTML!
+
+### YAML front matter parameters
+
+These are the main parameters you can place inside a page's YAML front matter that **Beautiful Jekyll** supports.
+
+Parameter   | Description
+----------- | -----------
+title       | Page or blog post title
+subtitle    | Short description of page or blog post that goes under the title
+tags        | List of tags to categorize the post. Separate the tags with commas and place them inside square brackets. Example: `[personal, self help, finance]`
+bigimg      | Include a large full-width image at the top of the page.  You can either give the path to a single image, or provide a list of images to cycle through (see [my personal website](https://deanattali.com/) as an example).
+comments    | If you want do add comments to a specific page, use `comments: true`. Comments are automatically enabled on blog posts; to turn comments off for a specific post, use `comments: false`. Comments only work if you enable at least one provider(diqus, staticman, just-comments) in `_config.yml` file.
+show-avatar | If you have an avatar configured in the `_config.yml` but you want to turn it off on a specific page, use `show-avatar: false`. If you want to turn it off by default, locate the line `show-avatar: true` in the file `_config.yml` and change the `true` to `false`; then you can selectively turn it on in specific pages using `show-avatar: true`.
+image       | If you want to add a personalized image to your blog post that will show up next to the post's excerpt and on the post itself, use `image: /path/to/img`.
+share-img   | If you want to specify an image to use when sharing the page on Facebook or Twitter, then provide the image's full URL here.
+social-share | If you don't want to show buttons to share a blog post on social media, use `social-share: false` (this feature is turned on by default).
+use-site-title | If you want to use the site title rather than page title as HTML document title (ie. browser tab title), use `use-site-title: true`. When set, the document title will take the format `Site Title - Site Description` (eg. `My website - A virtual proof that name is awesome!`). By default, it will use `Page Title` if it exists, or `Site Title` otherwise.
+layout      | What type of page this is (default is `post` for blog posts and `page` for other pages. You can use `minimal` if you don't want a header and footer)
+js          | List of local JavaScript files to include in the page (eg. `/js/mypage.js`)
+ext-js      | List of external JavaScript files to include in the page (eg. `//cdnjs.cloudflare.com/ajax/libs/underscore.js/1.8.2/underscore-min.js`). External JavaScript files that support [Subresource Integrity (SRI)](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) can be specified using the `href` and `sri` parameters eg.<br/>`href: "//code.jquery.com/jquery-3.1.1.min.js"`<br/>`sri: "sha256-hVVnYaiADRTO2PzUGmuLJr8BLUSjGIZsDYGmIJLv2b8="`
+css         | List of local CSS files to include in the page
+ext-css      | List of external CSS files to include in the page. External CSS files using SRI (see `ext-js` parameter) are also supported.
+googlefonts | List of Google fonts to include in the page (eg. `["Monoton", "Lobster"]`)
+gh-repo   | If you want to show GitHub buttons at the top of a post, this sets the GitHub repo name (eg. `daattali/beautiful-jekyll`). You must also use the `gh-badge` parameter to specify what buttons to show.
+gh-badge  | Select which GitHub buttons to display, available options are: [star, watch, fork, follow]. You must also use the `gh-repo` parameter to specify the GitHub repo.
+
+### Advanced features (including how to use a custom URL address for your site)
+
+I wrote [a blog post](https://deanattali.com/2015/03/12/beautiful-jekyll-how-to-build-a-site-in-minutes/) describing some more advanced features that I used in my website that are applicable to any Jekyll site.  It describes how I used a custom URL for my site (deanattali.com instead of daattali.github.io), how to add a Google-powered search into your site, and provides a few more details about having an RSS feed.
+
+## Creating a User Page vs a Project Page
+
+If you're not sure what the difference is, you can probably safely ignore this section.
+
+If you want to use this theme to host a website that will be available at `https://YOURUSERNAME.github.io`, then you do not need to read this section. That is called a User Page, you can only have one User Page in your GitHub account, and it is what you get by default when forking this project.
+
+If you want to use this theme to create a website for a particular repository, it will be available at `https://YOURUSERNAME.github.io/PROJECTNAME`, and that is called a [Project Page](https://help.github.com/articles/user-organization-and-project-pages/). You can have a Project Page for any repository you have on GitHub.
+
+**When using this theme for a Project Page, by default your website will be served from the `gh-pages` branch**, so you must take the following steps: 
+
+1. [Delete the existing `gh-pages` branch](https://help.github.com/en/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)
+
+2. [Create a new branch named `gh-pages` from the `master` branch](https://help.github.com/en/articles/creating-and-deleting-branches-within-your-repository#creating-a-branch)
+
+Alternatively, instead of the above two steps, you can opt to use the `master` branch instead of `gh-pages` branch as your website's source by choosing that option in the main Settings page. 
+
+## Showcased users (success stories!)
+
+To my huge surprise, Beautiful Jekyll has been used in over 500 websites in its first 6 months alone! Here is a hand-picked selection of some websites that use Beautiful Jekyll.
+
+Want your website featured here? [Contact me](https://deanattali.com/aboutme#contact) to let me know about your website.
+
+### Project/company websites
+
+| Website | Description |
+| :------ |:----------- |
+| [repidemicsconsortium.org/](https://www.repidemicsconsortium.org/) | R Epidemics Consortium |
+| [vaccineimpact.org](https://www.vaccineimpact.org/) | Vaccine Impact Modelling Consortium |
+| [derekogle.com/fishR](http://derekogle.com/fishR/) | Using R for Fisheries Analyses |
+| [bigdata.juju.solutions](http://bigdata.juju.solutions) | Creating Big Data solutions Juju Solutions |
+| [joecks.github.io/clipboard-actions](http://joecks.github.io/clipboard-actions/) | Clipboard Actions - an Android app |
+| [deanattali.com/shinyjs](http://deanattali.com/shinyjs/) | shinyjs - an R package |
+| [blabel.github.io](http://blabel.github.io) | Library for canonicalising blank node labels in RDF graphs |
+| [reactionic.github.io](http://reactionic.github.io) | Create iOS and Android apps with React and Ionic |
+| [ja2-stracciatella.github.io](http://ja2-stracciatella.github.io) | Jagged Alliance 2 Stracciatella |
+| [ddocent.com](http://ddocent.com/) | RADSeq Bioinformatics and Beyond |
+| [guitarlessons.org](https://www.guitarlessons.org/) | Free online guitar lessons for all |
+| [terremotocentroitalia.info](https://www.terremotocentroitalia.info/) | Information about the 2016 Italy earthquake |
+
+
+### Personal websites
+
+| Website | Who | What |
+| :------ |:--- | :--- |
+| [deanattali.com](https://deanattali.com) | Dean Attali | Creator of Beautiful Jekyll |
+| [ouzor.github.io](http://ouzor.github.io) | Juuso Parkkinen | Data scientist |
+| [derekogle.com](http://derekogle.com/) | Derek Ogle | Professor of Mathematical Sciences and Natural Resources |
+| [melyanna.github.io](http://melyanna.github.io/) | Melyanna | Shows off her nice art |
+| [chauff.github.io](http://chauff.github.io/) | Claudia Hauff | Professor at Delft University of Technology |
+| [kootenpv.github.io](http://kootenpv.github.io/) | Pascal van Kooten | Data analytics |
+| [sjackman.ca](http://sjackman.ca) | Shaun Jackman | PhD candidate in bioinformatics |
+| [anudit.in](http://www.anudit.in/) | Anudit Verma | Engineering student |
+| [sharepointoscar.github.io](http://sharepointoscar.github.io) | Oscar Medina | Independent Hacker |
+| [ocram85.com](https://ocram85.com) | Marco Blessing | A personal blog about PowerShell and automation |
+| [khanna.cc](https://khanna.cc/) | Harry Khanna | Law and software |
+
+## Advanced: Local development using Docker
+
+Beautiful Jekyll is meant to be so simple to use that you can do it all within the browser. However, if you'd like to develop locally on your own machine, that's possible too if you're comfortable with command line. Follow these simple steps set that up with Docker:
+
+1. Make sure you have [Docker](https://www.docker.com/) installed.
+
+2. Clone your repository locally.
+
+    ```bash
+    git clone https://github.com/<your_username>/<your_username>.github.io.git
+    ```
+
+3. Run the following shell commands to build the docker image and start the container for the first time:
+
+    ```bash
+    cd <repository_folder>
+    docker build -t beautiful-jekyll "$PWD"
+    docker run -d -p 4000:4000 --name beautiful-jekyll -v "$PWD":/srv/jekyll beautiful-jekyll
+    ```
+
+
+Now that Docker is set up, you do not need to run the above steps again. You can now view your website at http://localhost:4000/. You can start the container again in the future with:
+
+```bash
+docker start beautiful-jekyll
+```
+
+And you can stop the server with:
+
+```bash
+docker stop beautiful-jekyll
+```
+
+Whenever you make any changes to `_config.yml`, you must stop and re-start the server for the new config settings to take effect.
+
+Disclaimer: I personally am NOT using local development so I don't know much about running Jekyll locally. If you follow this route, please don't ask me questions because unfortunately I honestly won't be able to help!
+
+## FAQ and support
+
+If you need any help, I suggest heading over to the [Jekyll support forum](https://talk.jekyllrb.com/).
+
+Beautiful Jekyll is actively used by thousands of people with wildly varying degrees of competency, so it's impossible to answer all the questions that may arise. Below are answers to a few very common questions. Most questions that I get asked are not directly related to this theme, and instead are more general questions about Jekyll or web development. Many such questions can be answered by reading the [Jekyll documentation](https://jekyllrb.com/) or with Google.
+
+#### How do I change the number of posts per page OR the colour of the navigation bar OR the image in the navigation bar OR ...?
+
+Beautiful Jekyll is built to be very customizable, and as such, many questions about "how do I change ..." can be answered by looking at the `_config.yml` file. The configuration file has many adjustable parameters to customize your site.
+
+#### How do I add a favicon to my site?
+
+Easy! Just place a valid `favicon.ico` (or another valid favicon image) in the root directory of your project. And then wait! It can take a while to update.
+
+#### How do I move the blog to another page instead of having it on the home page?
+
+The default style of Beautiful Jekyll is to feature the blog feed on the front page. But for many sites that's not the ideal structure, and you may want to have a separate dedicated page for the blog posts. To have the blog hosted on a different URL (for example at `<mysite.com>/blog`), copy the `index.html` file into a folder with the same name as the desired page (for example, to `blog/index.html`), and in the `_config.yml` file you need to add a parameter `paginate_path: "/<page name>/page:num/"` (for example `paginate_path: "/blog/page:num/"`).
+
+#### What size do you recommend using for the `bigimg` photos?
+
+Unfortunately, this is a no-answer! There isn't a one-size-fits-all solution to this, because every person will view your site on a different browser with different dimensions. Some browsers will have very wide aspect ratio, some will be narrower, some will be vertical (such as phones), different phones have different screens, etc. The image will always be centered, so the only tip I can give is that you should make sure the important part of the image is in the middle so that it'll always show. Other than that, every browser will show a different clipping of the image.
+
+#### How do I use MathJax equations in my posts?
+
+MathJax can be easily integrated into your website with a one-line addition. You can see [this discussion](https://github.com/daattali/beautiful-jekyll/issues/195) for more information.
+
+#### My project page appear to be broken after a recent update!
+
+In June 2019, some URL related settings have been adjusted to be more in-line with how Jekyll uses them officially. Project Page absolute links might appear to be broken if you haven't propagated all necessary changes to your local templates, or if you have created additional templates making use of old settings. If a link contains a duplicated project path component, this is most likely the cause. In summary:
+
+| &nbsp; | Old behavior | New behavior |
+| --- | --- | --- |
+| `url` setting | `https://user.github.io/projectname` | (unset, GitHub auto detects) |
+| `baseurl` setting | `/projectname` | (unset, GitHub auto detects) |
+| Absolute link construction | `{{ site.url }}/your/path` | `{{ '/your/path' \| absolute_url }}` |
+| Relative link construction | `{{ site.baseurl }}/your/path` | `{{ '/your/path' \| relative_url }}` |
+
+## Credits
+
+This template was not made entirely from scratch. I would like to give special thanks to:
+- [Barry Clark](https://github.com/barryclark) and his project [Jekyll Now](https://github.com/barryclark/jekyll-now), from whom I've taken several ideas and code snippets, as well as some documenation tips.
+- [Iron Summit Media](https://github.com/IronSummitMedia) and their project [Bootstrap Clean Blog](https://github.com/IronSummitMedia/startbootstrap-clean-blog), from which I've used some design ideas and some of the templating code for posts and pagination.
+
+I'd also like to thank [Dr. Jekyll's Themes](https://drjekyllthemes.github.io/), [Jekyll Themes](http://jekyllthemes.org/), and another [Jekyll Themes](http://jekyllrc.github.io/jekyllthemes/) for featuring Beautiful Jekyll in their Jekyll theme directories.
+
+## Contributions
+
+If you find anything wrong or would like to contribute in any way, feel free to create a pull request/open an issue/send me a message.  Any comments are welcome!
+
+Thank you to [all contributors](https://github.com/daattali/beautiful-jekyll/graphs/contributors). Special thanks to  [@OCram85](https://github.com/OCram85) and [@abelcheung](https://github.com/abelcheung) for contributing multiple times as well as helping with discussions.
+
+If you do fork or clone this project to use as a template for your site, I would appreciate if you keep the link in the footer to this project.  I've noticed that several people who forked this repo removed the attribution and I would prefer to get the recognition if you do use this :)
+
+## Known limitations
+
+- If you have a project page and you want a custom 404 page, you must have a custom domain.  See https://help.github.com/articles/custom-404-pages/.  This means that if you have a regular User Page you can use the 404 page from this theme, but if it's a website for a specific repository, the 404 page will not be used.
+
+- If there are many navigation bar links and avatar, some of the links may get partially hidden behind the avatar. 

blog.bryanroessler.com/_config.yml

@@ -1,111 +1,179 @@
-# --- General options --- #
+###########################################################
+### Welcome to Beautiful Jekyll!
+### This config file is meant for settings that affect your entire website. When you first
+### set up your website you should go through all these settings and edit them, but after
+### the initial set up you won't need to come back to this file often.
+###########################################################
 
-# url is the full website URL
-# baseurl is the website's URL without the hostname
-
-# If you are building a simple GitHub user page (http://username.github.io) then use these settings:
-url: "https://blog.bryanroessler.com"
-baseurl: ""
-
-# If you are building a GitHub project page then use these settings:
-#url: "http://username.github.io/projectname"
-#baseurl: "/projectname"
-
-# Of course don't forget to change the username and projectname to YOUR username and project
+############################
+# --- Required options --- #
+############################
 
 # Name of website
 title: Bryan Roessler
 
-# Short description of your site
-description: Ordo ab chao
+# Your name to show in the footer
+author: Bryan Roessler
 
-# --- Navigation bar options --- #
+###############################################
+# --- List of links in the navigation bar --- #
+###############################################
 
-# List of links in the navigation bar
 navbar-links:
   Home: "https://bryanroessler.com"
   Blog: "https://blog.bryanroessler.com"
   CV: "https://cv.bryanroessler.com"
-  Repos: "https://git.bryanroessler.com"
+  Git: "https://git.bryanroessler.com"
   Services:
     - Syncthing: "https://syncthing.bryanroessler.com"
     - Panel: "https://panel.bryanroessler.com"
 
-# Image to show in the navigation bar - image must be a square (width = height)
+################
+# --- Logo --- #
+################
+
+# Image to show in the navigation bar - works best with a square image
 # Remove this parameter if you don't want an image in the navbar
-avatar: "/img/me_square_sepia_small.jpg"
+avatar: "/assets/img/me_square_sepia_small.jpg"
 
-# If you want to have an image logo in the top-left corner instead of the title text,
+# By default, the image is cut into a circle. You can disable this behaviour by setting 'round-avatar: false'
+round-avatar: true
+
+# If you want to have an image logo in the top-left corner instead of having the title of the website,
 # then specify the following parameter
-#title-img: "./img/me_square_sepia_small.jpg"
+#title-img: /path/to/image
 
-# --- Background colour/image options --- #
 
-# Personalize the colors in your website. Colour values can be any valid CSS colour
+#####################################
+# --- Footer social media links --- #
+#####################################
 
-navbar-col: "#F5F5F5"
-navbar-text-col: "#404040"
-navbar-children-col: "#F5F5F5"
-page-col: "#FFFFFF"
-link-col: "#008AFF"
-hover-col: "#0085A1"
-footer-col: "#F5F5F5"
-footer-text-col: "#777777"
-footer-link-col: "#404040"
+# Select the social network links that you want to show in the footer.
+# You can change the order that they show up on the page by changing the order here.
+# Uncomment the links you want to show and add your information to each one.
 
-# Alternatively, the navbar, footer, and page background can be set to use background images
-# instead of colour
-
-# navbar-img: "/img/bgimage.png"
-# footer-img: "/img/bgimage.png"
-# page-img: "/img/bgimage.png"
-
-# --- Footer options --- #
-
-# Change all these values or delete the ones you don't want.
-# Important: you must keep the "name" parameter, everything else you can remove
-author:
-  name: Bryan Roessler
-
-# Select your active Social Network Links.
-# Uncomment the links you want to show in the footer and add your information to each link.
-# You can reorder the items to define the link order.
-# If you want to add a new link that isn't here, you'll need to also edit the file _data/SocialNetworks.yml
 social-network-links:
-  rss: true
   email: "bryanroessler@gmail.com"
-#  facebook: daattali
+  rss: true
+# facebook:
   github: "https://git.bryanroessler.com"
-#  twitter: daattali
-#  reddit: yourname
-#  google-plus: +DeanAttali
+# twitter:
+# reddit:
+# google-plus:
   linkedin: bryan-roessler-phd-47535a60
-#  xing: yourname
-#  stackoverflow: "3943160/daattali"
-#  snapchat: deanat78
-#  instagram: deanat78
-#  youtube: user/deanat78
+# youtube:
+# medium:
 # spotify: yourname
 # telephone: +14159998888
 # steam: deanat78
 # twitch: yourname
 # yelp: yourname
+# telegram: yourname
+# calendly: yourname
+# mastodon: instance.url/@username
+# bluesky: yourname
+# ORCID: your ORCID ID
+# google-scholar: your google scholar
+# discord: "invite_code" or "users/userid" or "invite/invite_code"
+# kaggle: yourname
+# hackerrank: yourname
+# gitlab: yourname
+# itchio: yourname
+# untappd: yourname
 
-# Select which share links to show in posts
+# If you want your website to generate an RSS feed, provide a description
+# The URL for the feed will be https://<your_website>/feed.xml
+rss-description: Bryan Roessler's Blog
+
+###########################
+# --- General options --- #
+###########################
+
+# Select which social network share links to show in posts
 share-links-active:
   twitter: false
   facebook: false
-  google: false
   linkedin: false
+  vk: false
 
 # How to display the link to the website in the footer
 # Remove this if you don't want a link in the footer
-url-pretty: "bryanroessler.com"  # eg. "deanattali.com/beautiful-jekyll"
+url-pretty: "bryanroessler.com"
 
-# --- Web Statistics Section --- #
+# Add the website title to the title of every page
+title-on-all-pages: true
+
+# Excerpt word length - Truncate the excerpt of each post on the feed page to the specified number of words
+excerpt_length: 50
+
+# Whether or not to show an excerpt for every blog post in the feed page
+feed_show_excerpt: true
+
+# Whether or not to show a list of tags below each post preview in the feed page
+feed_show_tags: true
+
+# Add a search button to the navbar
+post_search: true
+
+# Add a button in the footer to edit the current page. Only works if your website is hosted on GitHub
+edit_page_button: true
+
+# Allow sub-menu items (second-level navigation menu items) to be longer than the top-level menu
+# If this setting is off, then long sub-menu words might get cut off
+# See https://github.com/daattali/beautiful-jekyll/issues/765 to understand the issue this setting can solve
+navbar-var-length: false
+
+# The keywords to associate with your website, for SEO purposes
+#keywords: "my,list,of,keywords"
+
+######################################
+# --- Colours / background image --- #
+######################################
+
+# Personalize the colours in your website. Colour values can be any valid CSS colour
+
+page-col: "#FFFFFF"
+text-col: "#404040"
+link-col: "#008AFF"
+hover-col: "#0085A1"
+navbar-col: "#F5F5F5" # #EAEAEA
+navbar-text-col: "#404040"
+navbar-border-col: "#DDDDDD"
+footer-col: "#F5F5F5" # #EAEAEA
+footer-text-col: "#777777"
+footer-link-col: "#404040"
+footer-hover-col: "#0085A1"
+
+# Alternatively, the navbar, footer, and page background can be set to an image
+# instead of colour
+
+#navbar-img: "/assets/img/bgimage.png"
+#footer-img: "/assets/img/bgimage.png"
+#page-img: "/assets/img/bgimage.png"
+
+# Suggest a colour for mobile browsers to use as the browser's theme. This is only supported by a few mobile browsers.
+#mobile-theme-col: "#0085A1"
+
+# For any extra visual customization, you can include additional CSS files in every page on your site. List any custom CSS files here
+#site-css:
+#  - "/assets/css/custom-styles.css"
+
+# If you have common JavaScript files that should be included in every page, list them here
+#site-js:
+#  - "/assets/js/custom-script.js"
+
+#################################
+# --- Web Analytics Section --- #
+#################################
+
+# Fill in your Google Analytics tag ID (or "Measurement ID") to track your website usage
+#gtag: "G-XXXXXXXXXX"
+
+# Fill in your Cloudflare Analytics beacon token to track your website using Cloudflare Analytics
+#cloudflare_analytics: ""
 
 # Fill in your Google Analytics ID to track your website using GA
-#google_analytics: ""
+google_analytics: "UA-158358388-1"
 
 # Google Tag Manager ID
 #gtm: ""
@@ -113,34 +181,82 @@ url-pretty: "bryanroessler.com"  # eg. "deanattali.com/beautiful-jekyll"
 # Matomo (aka Piwik) Web statistics
 # Uncomment the following section to enable Matomo. The opt-out parameter controls
 # whether or not you want to allow users to opt out of tracking.
-
 #matomo:
 #  site_id: "9"
 #  uri: "demo.wiki.pro"
 #  opt-out: true
 
+# Google Universal Analytics ID -- deprecated
+# As of July 2023 this is no longer supported by Google! If you are still using `google_analytics`,
+# you should switch to using the `gtag` field above instead.
+#google_analytics: "UA-XXXXXXXX-X"
+
+####################
 # --- Comments --- #
+####################
 
-# Fill in your Disqus shortname (NOT the userid) if you want to support Disqus comments
-# disqus: ""
+# To use Disqus comments, sign up to https://disqus.com and fill in your Disqus shortname (NOT the userid)
+#disqus: ""
 
-# To use Facebook Comments, fill in a Facebook App ID
-# fb_comment_id: ""
+# To use Facebook Comments, create a Facebook app and fill in the Facebook App ID
+#fb_comment_id: ""
 
+# To use CommentBox, sign up for a Project ID on https://commentbox.io
+#commentbox: "" # Project ID, e.g. "5694267682979840-proj"
+
+# To use Utterances comments: (0) uncomment the following section, (1) fill in
+# "repository" (make sure the repository is public), (2) Enable Issues in your repository,
+# (3) Install the Utterances app in your repository https://github.com/apps/utterances
+# See more details about the parameters below at https://utteranc.es/
+#utterances:
+#  repository: # GitHub username/repository eg. "daattali/beautiful-jekyll"
+#  issue-term: title   # Mapping between blog posts and GitHub issues
+#  theme: github-light # Utterances theme
+#  label: blog-comments # Label that will be assigned to GitHub Issues created by Utterances
+
+# To use Staticman comments, uncomment the following section. You may leave the reCaptcha
+# section commented if you aren't using reCaptcha for spam protection.
+# Using Staticman requires advanced knowledge, please consult
+# https://github.com/eduardoboucas/staticman/ and https://staticman.net/ for further
+# instructions. For any support with staticman please direct questions to staticman and
+# not to BeautifulJekyll.
+#staticman:
+#  repository : # GitHub username/repository eg. "daattali/beautiful-jekyll"
+#  branch     : master # If you're not using `master` branch, then you also need to update the `branch` parameter in `staticman.yml`
+#  endpoint   : # URL of your deployment, with a trailing slash eg. "https://<your-api>/v3/entry/github/"
+#  reCaptcha:   # (optional, set these parameters in `staticman.yml` as well)
+#    siteKey  : # You need to apply for a site key on Google
+#    secret   : # Encrypt your password by going to https://<your-own-api>/v3/encrypt/<your-site-secret>
+
+# To use giscus comments:
+# (0) Uncomment the following giscus section, (1) Enable Discussions in your GitHub repository,
+# (2) Install the giscus app in your repository (details at https://giscus.app),
+# (3) Fill in *all* the parameters below
+# See more details about giscus and each of the following parameters at https://giscus.app
+#giscus:
+#  hostname: giscus.app # Replace with your giscus instance's hostname if self-hosting
+#  repository: # GitHub username/repository eg. "daattali/beautiful-jekyll"
+#  repository-id: # ID of your repository, retrieve this info from https://giscus.app
+#  category: Announcements # Category name of your GitHub Discussion posts
+#  category-id: # ID of your category, retrieve this info from https://giscus.app
+#  mapping: pathname
+#  reactions-enabled: 1
+#  emit-metadata: 0
+#  theme: light
+
+################
 # --- Misc --- #
+################
+
+# Ruby Date Format to show dates of posts
+date_format: "%B %-d, %Y"
 
 # Facebook App ID
-# fb_app_id: ""
+#fb_app_id: ""
 
-# Excerpt Word Length
-# Truncates the excerpt to the specified number of words on the index page
-excerpt_length: 50
-
-# Character used to separate site title and description in HTML document title
-# and RSS feed title
-title-separator: "-"
-
-# --- Don't need to touch anything below here (but you can if you want) --- #
+#################################################################################
+# --- You don't need to touch anything below here (but you can if you want) --- #
+#################################################################################
 
 # Output options (more information on Jekyll's site)
 timezone: "America/New_York"
@@ -149,6 +265,8 @@ highlighter: rouge
 permalink: /:year-:month-:day-:title/
 paginate: 5
 
+plugins: [jekyll-paginate]
+
 kramdown:
   input: GFM
 
@@ -160,89 +278,27 @@ defaults:
       type: "posts"
     values:
       layout: "post"
-      comments: true  # add comments to all blog posts
+      comments: false  # add comments to all blog posts
       social-share: true # add social media sharing buttons to all blog posts
+      readtime: true # add estimated reading time on all blog posts
   -
     scope:
-      path: "" # all files
+      path: "" # any file that's not a post will be a "page" layout by default
     values:
       layout: "page"
-      show-avatar: true
-
-# Use tags index page and make tags on each post clickable
-link-tags: true
 
 # Exclude these files from production site
 exclude:
-  - Gemfile
-  - Gemfile.lock
-  - node_modules
-  - vendor/bundle/
-  - vendor/cache/
-  - vendor/gems/
-  - vendor/ruby/
   - CHANGELOG.md
   - CNAME
-  - Dockerfile
+  - Gemfile
+  - Gemfile.lock
   - LICENSE
   - README.md
-  - Vagrantfile
-
-# prose.io config
-prose:
-  rooturl: '_posts'
-  media: 'img'
-  ignore:
-    - 404.html
-    - LICENSE
-    - feed.xml
-    - _config.yml
-    - /_layouts
-    - /_includes
-    - /css
-    - /img
-    - /js
-  metadata:
-    _posts:
-      - name: "layout"
-        field:
-          element: "hidden"
-          value: "post"
-      - name: "title"
-        field:
-          element: "text"
-          label: "Post title"
-          placeholder: "Title"
-          alterable: true
-      - name: "subtitle"
-        field:
-          element: "textarea"
-          label: "Subtitle"
-          placeholder: "A description of your post."
-          alterable: true
-      - name: "date"
-        field:
-          element: "text"
-          label: "Date"
-          help: "Enter date of post."
-          placeholder: "yyyy-mm-dd"
-          alterable: true
-      - name: "image"
-        field:
-          element: "text"
-          label: "Image"
-          help: "Add a thumbnail image to your post."
-          placeholder: "Thumbnail"
-          alterable: true
-      - name: "published"
-        field:
-          element: "checkbox"
-          label: "Publish"
-          help: "Check to publish post, uncheck to hide."
+  - screenshot.png
+  - docs/
+  - vendor/
 
 plugins:
   - jekyll-paginate
   - jekyll-sitemap
-
-# Beautiful Jekyll / Dean Attali
-# 2fc73a3a967e97599c9763d05e564189

blog.bryanroessler.com/_data/SocialNetworks.yml

@@ -13,7 +13,7 @@ facebook:
 
 github:
   name: "GitHub"
-  baseURL: ""
+  baseURL: "https://github.com/"
   icon: "fa-github"
 
 twitter:
@@ -26,11 +26,6 @@ reddit:
   baseURL: "https://reddit.com/u/"
   icon: "fa-reddit"
 
-google-plus:
-  name: "Google+"
-  baseURL: "https://plus.google.com/"
-  icon: "fa-google-plus"
-
 email:
   name: "Email me"
   baseURL: "mailto:"
@@ -78,7 +73,7 @@ telephone:
 
 rss:
   name: "RSS"
-  baseURL: "{{ '/feed.xml' | prepend: site.baseurl }}"
+  baseURL: "{{ '/feed.xml' | relative_url }}"
   icon: "fa-rss"
 
 steam:

blog.bryanroessler.com/_data/ui-text.yml

@@ -0,0 +1,494 @@
+# User interface text and labels
+
+# English (default)
+# -----------------
+en: &DEFAULT_EN
+  comments_label             : "Leave a comment"
+  comments_title             : "Comments"
+  comment_form_info          : "Your email address will not be published. Required fields are marked"
+  comment_form_comment_label : "Comment"
+  comment_form_md_info       : "Markdown is supported."
+  comment_form_name_label    : "Name"
+  comment_form_email_label   : "Email address"
+  comment_form_website_label : "Website (optional)"
+  comment_btn_submit         : "Submit comment"
+  comment_btn_submitted      : "Submitted"
+  comment_success_msg        : "Thanks for your comment! It will show on the site once it has been approved."
+  comment_error_msg          : "Sorry, there was an error with your submission. Please make sure all required fields have been completed and try again."
+en-US:
+  <<: *DEFAULT_EN
+en-CA:
+  <<: *DEFAULT_EN
+en-GB:
+  <<: *DEFAULT_EN
+en-AU:
+  <<: *DEFAULT_EN
+
+# Spanish
+# -------
+es: &DEFAULT_ES
+  comments_label             : "Dejar un commentario"
+  comments_title             : "Comentar"
+  comment_form_info          : "Su dirección de correo no será publicada. Se han resaltado los campos requeridos"
+  comment_form_comment_label : "Comentario"
+  comment_form_md_info       : "Markdown está soportado."
+  comment_form_name_label    : "Nombre"
+  comment_form_email_label   : "Dirección de E-mail"
+  comment_form_website_label : "Sitio web (opcional)"
+  comment_btn_submit         : "Enviar Commentario"
+  comment_btn_submitted      : "Enviado"
+  comment_success_msg        : "Gracias por su comentario!, Este se visualizará en el sitio una vez haya sido aprobado"
+  comment_error_msg          : "Lo sentimos, ha ocurrido un error al enviar su comentario. Por favor asegurese que todos los campos han sido diligenciados e intente de nuevo"
+es-ES:
+  <<: *DEFAULT_ES
+es-CO:
+  <<: *DEFAULT_ES
+
+# French
+# ------
+fr: &DEFAULT_FR
+  comments_label             : "Laisser un commentaire"
+  comments_title             : "Commentaires"
+  comment_form_info          : "Votre adresse email ne sera pas visible. Les champs obligatoires sont marqués"
+  comment_form_comment_label : "Commentaire"
+  comment_form_md_info       : "Markdown est supporté."
+  comment_form_name_label    : "Nom"
+  comment_form_email_label   : "Adresse mail"
+  comment_form_website_label : "Site web (optionnel)"
+  comment_btn_submit         : "Envoyer"
+  comment_btn_submitted      : "Envoyé"
+  comment_success_msg        : "Merci pour votre commentaire, il sera visible sur le site une fois approuvé."
+  comment_error_msg          : "Désolé, une erreur est survenue lors de la soumission. Vérifiez que les champs obligatoires ont été remplis et réessayez."
+fr-FR:
+  <<: *DEFAULT_FR
+fr-BE:
+  <<: *DEFAULT_FR
+fr-CH:
+  <<: *DEFAULT_FR
+
+# Turkish
+# -------
+tr: &DEFAULT_TR
+  comments_label             : "Yorum yapın"
+  comments_title             : "Yorumlar"
+  comment_form_info          : "Email adresiniz gösterilmeyecektir. Zorunlu alanlar işaretlenmiştir"
+  comment_form_comment_label : "Yorumunuz"
+  comment_form_md_info       : "Markdown desteklenmektedir."
+  comment_form_name_label    : "Adınız"
+  comment_form_email_label   : "Email adresiniz"
+  comment_form_website_label : "Websiteniz (opsiyonel)"
+  comment_btn_submit         : "Yorum Yap"
+  comment_btn_submitted      : "Gönderildi"
+  comment_success_msg        : "Yorumunuz için teşekkürler! Yorumunuz onaylandıktan sonra sitede gösterilecektir."
+  comment_error_msg          : "Maalesef bir hata oluştu. Lütfen zorunlu olan tüm alanları doldurduğunuzdan emin olun ve sonrasında tekrar deneyin."
+tr-TR:
+  <<: *DEFAULT_TR
+
+# Portuguese
+# ----------
+pt: &DEFAULT_PT
+  comments_label             : "Deixe um Comentário"
+  comments_title             : "Comentários"
+  comment_form_info          : "O seu endereço email não será publicado. Os campos obrigatórios estão assinalados"
+  comment_form_comment_label : "Comentário"
+  comment_form_md_info       : "Markdown é suportado."
+  comment_form_name_label    : "Nome"
+  comment_form_email_label   : "Endereço Email"
+  comment_form_website_label : "Site (opcional)"
+  comment_btn_submit         : "Sumbeter Comentário"
+  comment_btn_submitted      : "Submetido"
+  comment_success_msg        : "Obrigado pelo seu comentário! Será visível no site logo que aprovado."
+  comment_error_msg          : "Lamento, ocorreu um erro na sua submissão. Por favor verifique se todos os campos obrigatórios estão corretamente preenchidos e tente novamente."
+pt-PT:
+  <<: *DEFAULT_PT
+# Brazilian Portuguese
+pt-BR:
+  comments_label             : "Deixe um comentário"
+  comments_title             :
+  comment_form_info          : "Seu email não será publicado. Os campos obrigatórios estão marcados"
+  comment_form_comment_label : "Comentário"
+  comment_form_md_info       : "Markdown é suportado."
+  comment_form_name_label    : "Nome"
+  comment_form_email_label   : "Email"
+  comment_form_website_label : "Site (opcional)"
+  comment_btn_submit         : "Enviar Comentário"
+  comment_btn_submitted      : "Enviado"
+  comment_success_msg        : "Obrigado pelo seu comentário! Ele aparecerá no site assim que for aprovado."
+  comment_error_msg          : "Desculpe, ocorreu um erro no envio. Por favor verifique se todos os campos obrigatórios foram preenchidos e tente novamente."
+
+# Italian
+# -------
+it: &DEFAULT_IT
+  comments_label             : "Scrivi un commento"
+  comments_title             :
+  comment_form_info          : "Il tuo indirizzo email non sarà pubblicato. Sono segnati i campi obbligatori"
+  comment_form_comment_label : "Commenta"
+  comment_form_md_info       : "Il linguaggio Markdown è supportato"
+  comment_form_name_label    : "Nome"
+  comment_form_email_label   : "Indirizzo email"
+  comment_form_website_label : "Sito Web (opzionale)"
+  comment_btn_submit         : "Invia commento"
+  comment_btn_submitted      : "Inviato"
+  comment_success_msg        : "Grazie per il tuo commento! Verrà visualizzato nel sito una volta che sarà approvato."
+  comment_error_msg          : "C'è stato un errore con il tuo invio. Assicurati che tutti i campi richiesti siano stati completati e riprova."
+it-IT:
+  <<: *DEFAULT_IT
+
+# Chinese  (zh-CN Chinese - China)
+# --------------------------------
+zh: &DEFAULT_ZH_HANS
+  comments_label             : "留下评论"
+  comments_title             : "评论"
+  comment_form_info          : "您的电子邮箱地址并不会被展示。请填写标记为必须的字段。"
+  comment_form_comment_label : "评论"
+  comment_form_md_info       : "Markdown语法已支持。"
+  comment_form_name_label    : "姓名"
+  comment_form_email_label   : "电子邮箱"
+  comment_form_website_label : "网站（可选）"
+  comment_btn_submit         : "提交评论"
+  comment_btn_submitted      : "已提交"
+  comment_success_msg        : "感谢您的评论！被批准后它会立即在此站点展示。"
+  comment_error_msg          : "很抱歉，您的提交存在错误。请确保所有必填字段都已填写正确，然后再试一次。"
+zh-CN:
+  <<: *DEFAULT_ZH_HANS
+zh-SG:
+  <<: *DEFAULT_ZH_HANS
+# Taiwan (Traditional Chinese)
+zh-TW: &DEFAULT_ZH_HANT
+  comments_label             : "留言"
+  comments_title             : "留言內容"
+  comment_form_comment_label : "留言內容"
+  comment_form_md_info       : "支援Markdown語法。"
+  comment_form_name_label    : "名字"
+  comment_form_email_label   : "電子信箱帳號"
+  comment_form_website_label : "網頁 (可選填)"
+  comment_btn_submit         : "送出留言"
+  comment_btn_submitted      : "已送出"
+  comment_success_msg        : "感謝您的留言！ 審核後將會顯示在站上。"
+  comment_error_msg          : "抱歉，部份資料輸入有問題。請確認資料填寫正確後再試一次。"
+zh-HK:
+  <<: *DEFAULT_ZH_HANT
+
+# German / Deutsch
+# ----------------
+de: &DEFAULT_DE
+  comments_label             : "Hinterlasse einen Kommentar"
+  comments_title             : "Kommentare"
+  comment_form_info          : "Die E-Mail Adresse wird nicht veröffentlicht. Benötigte Felder sind markiert"
+  comment_form_comment_label : "Kommentar"
+  comment_form_md_info       : "Markdown wird unterstützt."
+  comment_form_name_label    : "Name"
+  comment_form_email_label   : "E-Mail-Adresse"
+  comment_form_website_label : "Webseite (optional)"
+  comment_btn_submit         : "Kommentar absenden"
+  comment_btn_submitted      : "Versendet"
+  comment_success_msg        : "Danke für den Kommentar! Er wird nach Prüfung auf der Seite angezeigt."
+  comment_error_msg          : "Entschuldigung, es gab einen Fehler. Bitte fülle alle benötigten Felder aus und versuche es erneut."
+de-DE:
+  <<: *DEFAULT_DE
+de-AT:
+  <<: *DEFAULT_DE
+de-CH:
+  <<: *DEFAULT_DE
+de-BE:
+  <<: *DEFAULT_DE
+de-LI:
+  <<: *DEFAULT_DE
+de-LU:
+  <<: *DEFAULT_DE
+
+# Nepali (Nepal)
+# --------------
+ne: &DEFAULT_NE
+  comments_label             : "टिप्पणी दिनुहोस्"
+  comments_title             : "टिप्पणीहरू"
+  comment_form_info          : "तपाइँको इमेल ठेगाना प्रकाशित गरिने छैन।आवश्यक जानकारीहरुमा चिन्ह लगाइको छ"
+  comment_form_comment_label : "टिप्पणी"
+  comment_form_md_info       : "मार्कडाउन  समर्थित छ।"
+  comment_form_name_label    : "नाम"
+  comment_form_email_label   : "इमेल ठेगाना"
+  comment_form_website_label : "वेबसाइट (वैकल्पिक)"
+  comment_btn_submit         : "टिप्पणी दिनुहोस् "
+  comment_btn_submitted      : "टिप्पणी भयो"
+  comment_success_msg        : "तपाईंको टिप्पणीको लागि धन्यवाद! एक पटक यो अनुमोदन गरेपछी यो साइटमा देखाउनेछ।"
+  comment_error_msg          : "माफ गर्नुहोस्, तपाईंको टिप्पणी त्रुटि थियो।सबै आवश्यक जानकारीहरु पूरा गरिएको छ भने निश्चित गर्नुहोस् र फेरि प्रयास गर्नुहोस्।"
+ne-NP:
+  <<: *DEFAULT_NE
+
+# Korean
+# ------
+ko: &DEFAULT_KO
+  comments_label             : "댓글남기기"
+  comments_title             : "댓글"
+  comment_form_info          : "이메일은 공개되지 않습니다. 작성 필요 필드:"
+  comment_form_comment_label : "댓글"
+  comment_form_md_info       : "마크다운을 지원합니다."
+  comment_form_name_label    : "이름"
+  comment_form_email_label   : "이메일"
+  comment_form_website_label : "웹사이트(선택사항)"
+  comment_btn_submit         : "댓글 등록"
+  comment_btn_submitted      : "등록됨"
+  comment_success_msg        : "감사합니다! 댓글이 머지된 후 확인하실 수 있습니다."
+  comment_error_msg          : "댓글 등록에 문제가 있습니다. 필요 필드를 작성했는지 확인하고 다시 시도하세요."
+ko-KR:
+  <<: *DEFAULT_KO
+
+# Russian / Русский
+# -----------------
+ru: &DEFAULT_RU
+  comments_label             : "Оставить комментарий"
+  comments_title             : "Комментарии"
+  comment_form_info          : "Ваш адрес электронной почты не будет опубликован. Обязательные поля помечены"
+  comment_form_comment_label : "Комментарий"
+  comment_form_md_info       : "Поддерживается синтаксис Markdown."
+  comment_form_name_label    : "Имя"
+  comment_form_email_label   : "Электронная почта"
+  comment_form_website_label : "Ссылка на сайт (необязательно)"
+  comment_btn_submit         : "Оставить комментарий"
+  comment_btn_submitted      : "Отправлено"
+  comment_success_msg        : "Спасибо за Ваш комментарий! Он будет опубликован на сайте после проверки."
+  comment_error_msg          : "К сожалению, произошла ошибка с отправкой комментария. Пожалуйста, убедитесь, что все обязательные поля заполнены и попытайтесь снова."
+ru-RU:
+  <<: *DEFAULT_RU
+
+# Lithuanian / Lietuviškai
+# ------------------------
+lt: &DEFAULT_LT
+  comments_label             : "Palikti komentarą"
+  comments_title             : "Komentaras"
+  comment_form_info          : "El. pašto adresas nebus viešinamas. Būtini laukai pažymėti"
+  comment_form_comment_label : "Komentaras"
+  comment_form_md_info       : "Markdown palaikomas."
+  comment_form_name_label    : "Vardas"
+  comment_form_email_label   : "El. paštas"
+  comment_form_website_label : "Tinklapis (nebūtina)"
+  comment_btn_submit         : "Komentuoti"
+  comment_btn_submitted      : "Įrašytas"
+  comment_success_msg        : "Ačiū už komentarą! Jis bus parodytas kai bus patvirtintas."
+  comment_error_msg          : "Atleiskite, įvyko netikėta klaida įrašant komentarą. Pasitikrinkite ar užpildėte visus būtinus laukus ir pamėginkite dar kartą."
+lt-LT:
+  <<: *DEFAULT_LT
+
+# Greek
+# -----
+gr: &DEFAULT_GR
+  comments_label             : "Αφήστε ένα σχόλιο"
+  comments_title             : "Σχόλια"
+  comment_form_info          : "Η διεύθυνση email σας δεν θα δημοσιευθεί. Τα απαιτούμενα πεδία εμφανίζονται με αστερίσκο"
+  comment_form_comment_label : "Σχόλιο"
+  comment_form_md_info       : "Το πεδίο υποστηρίζει Markdown."
+  comment_form_name_label    : "Όνομα"
+  comment_form_email_label   : "Διεύθυνση email"
+  comment_form_website_label : "Ιστοσελίδα (προαιρετικό)"
+  comment_btn_submit         : "Υπόβαλε ένα σχόλιο"
+  comment_btn_submitted      : "Έχει υποβληθεί"
+  comment_success_msg        : "Ευχαριστούμε για το σχόλιό σας! Θα εμφανιστεί στην ιστοσελίδα αφού εγκριθεί."
+  comment_error_msg          : "Λυπούμαστε, παρουσιάστηκε σφάλμα με την υποβολή σας. Παρακαλούμε βεβαιωθείτε ότι έχετε όλα τα απαιτούμενα πεδία συμπληρωμένα και δοκιμάστε ξανά."
+gr-GR:
+  <<: *DEFAULT_GR
+
+# Swedish
+# -------
+sv: &DEFAULT_SV
+  comments_label             : "Lämna en kommentar"
+  comments_title             : "Kommentarer"
+  comment_form_info          : "Din e-post adress kommer inte att publiceras. Obligatoriska fält är markerade"
+  comment_form_comment_label : "Kommentar"
+  comment_form_md_info       : "Använd Markdown för text-formateringen."
+  comment_form_name_label    : "Namn"
+  comment_form_email_label   : "E-post adress"
+  comment_form_website_label : "Webdsida (valfritt)"
+  comment_btn_submit         : "Skicka en kommentar"
+  comment_btn_submitted      : "Kommentaren har tagits emot"
+  comment_success_msg        : "Tack för din kommentar! Den kommer att visas på sidan så fort den har godkännts."
+  comment_error_msg          : "Tyvärr det har blivit något fel i en av fälten, se till att du fyller i alla rutor och försök igen."
+sv-SE:
+  <<: *DEFAULT_SV
+sv-FI:
+  <<: *DEFAULT_SV
+
+# Dutch
+# -----
+nl: &DEFAULT_NL
+  comments_label             : "Laat een reactie achter"
+  comments_title             : "Commentaren"
+  comment_form_info          : "Uw e-mailadres wordt niet gepubliceerd. Verplichte velden zijn gemarkeerd"
+  comment_form_comment_label : "Commentaar"
+  comment_form_md_info       : "Markdown wordt ondersteund."
+  comment_form_name_label    : "Naam"
+  comment_form_email_label   : "E-mailadres"
+  comment_form_website_label : "Website (optioneel)"
+  comment_btn_submit         : "Commentaar toevoegen"
+  comment_btn_submitted      : "Toegevoegd"
+  comment_success_msg        : "Bedankt voor uw reactie! Het zal op de site worden weergegeven zodra het is goedgekeurd."
+  comment_error_msg          : "Sorry, er is een fout opgetreden bij uw inzending. Zorg ervoor dat alle vereiste velden zijn voltooid en probeer het opnieuw."
+nl-BE:
+  <<: *DEFAULT_NL
+nl-NL:
+  <<: *DEFAULT_NL
+
+# Indonesian
+# ----------
+id: &DEFAULT_ID
+  comments_label             : "Tinggalkan komentar"
+  comments_title             : "Komentar"
+  comment_form_info          : "Email Anda tidak akan dipublish. Kolom yang diperlukan ditandai"
+  comment_form_comment_label : "Komentar"
+  comment_form_md_info       : "Markdown disupport."
+  comment_form_name_label    : "Nama"
+  comment_form_email_label   : "Alamat email"
+  comment_form_website_label : "Website (opsional)"
+  comment_btn_submit         : "Submit Komentar"
+  comment_btn_submitted      : "Telah disubmit"
+  comment_success_msg        : "Terimakasih atas komentar Anda! Komentar ini akan tampil setelah disetujui."
+  comment_error_msg          : "Maaf, ada kesalahan pada submisi Anda. Pastikan seluruh kolom sudah dilengkapi dan coba kembali."
+id-ID:
+  <<: *DEFAULT_ID
+
+# Vietnamese
+# ----------
+vi: &DEFAULT_VI
+  comments_label             : "Để lại bình luận"
+  comments_title             : "Bình luận"
+  comment_form_info          : "Email của bạn sẽ được giữ bí mật. Các phần bắt buộc được đánh dấu"
+  comment_form_comment_label : "Bình luận"
+  comment_form_md_info       : "Hỗ trợ Markdown."
+  comment_form_name_label    : "Tên"
+  comment_form_email_label   : "Địa chỉ email"
+  comment_form_website_label : "Website (không bắt buộc)"
+  comment_btn_submit         : "Gửi bình luận"
+  comment_btn_submitted      : "Đã được gửi"
+  comment_success_msg        : "Cảm ơn bạn đã bình luận! Bình luận sẽ xuất hiện sau khi được duyệt."
+  comment_error_msg          : "Rất tiếc, có lỗi trong việc gửi bình luận. Hãy đảm bảo toàn bộ các phần bắt buộc đã được điền đầy đủ và thử lại."
+vi-VN:
+  <<: *DEFAULT_VI
+
+# Danish
+# ------
+da: &DEFAULT_DA
+  comments_label             : "Skriv en kommentar"
+  comments_title             : "Kommentarer"
+  comment_form_info          : "Din e-mail bliver ikke offentliggjort. Obligatoriske felter er markeret"
+  comment_form_comment_label : "Kommentar"
+  comment_form_md_info       : "Markdown er understøttet."
+  comment_form_name_label    : "Navn"
+  comment_form_email_label   : "E-mail"
+  comment_form_website_label : "Website (frivillig)"
+  comment_btn_submit         : "Send kommentar"
+  comment_btn_submitted      : "Sendt"
+  comment_success_msg        : "Tak for din kommentar! Den bliver vist på siden, så snart den er godkendt."
+  comment_error_msg          : "Desværre skete der en fejl. Prøv igen, mens du sørger for at alle obligatoriske felter er udfyldt."
+da-DK:
+  <<: *DEFAULT_DA
+
+# Polish
+# ------
+pl: &DEFAULT_PL
+  comments_label             : "Zostaw komentarz"
+  comments_title             : "Komentarze"
+  comment_form_info          : "Twój adres email nie będzie udostępiony. Wymagane pola są oznaczone"
+  comment_form_comment_label : "Skomentuj"
+  comment_form_md_info       : "Markdown jest wspierany"
+  comment_form_name_label    : "Imię"
+  comment_form_email_label   : "Adres email"
+  comment_form_website_label : "Strona www (opcjonalna)"
+  comment_btn_submit         : "Skomentuj"
+  comment_btn_submitted      : "Komentarz dodany"
+  comment_success_msg        : "Dziękuję za Twój komentarz! Zostanie dodany po akceptacji."
+  comment_error_msg          : "Niestety wystąpił błąd. Proszę upewnij się, że wszystkie wymagane pola zostały wypełnione i spróbuj ponownie."
+pl-PL:
+  <<: *DEFAULT_PL
+
+# Japanese
+# --------
+ja: &DEFAULT_JA
+  comments_label             : "コメントする"
+  comments_title             : "コメント"
+  comment_form_info          : "メールアドレスが公開されることはありません。次の印のある項目は必ず入力してください:"
+  comment_form_comment_label : "コメント"
+  comment_form_md_info       : "Markdown を使用できます"
+  comment_form_name_label    : "名前"
+  comment_form_email_label   : "メールアドレス"
+  comment_form_website_label : "URL (任意)"
+  comment_btn_submit         : "コメントを送信する"
+  comment_btn_submitted      : "送信しました"
+  comment_success_msg        : "コメントありがとうございます！　コメントは承認されるとページに表示されます。"
+  comment_error_msg          : "送信エラーです。必須項目がすべて入力されていることを確認して再送信してください。"
+ja-JP:
+  <<: *DEFAULT_JA
+
+# Slovak
+# -----------------
+sk: &DEFAULT_SK
+  comments_label             : "Zanechaj odkaz"
+  comments_title             : "Komentáre"
+  comment_form_info          : "Tvoja emailová adresa nebude publikovaná. Požadované polia sú označené"
+  comment_form_comment_label : "Komentár"
+  comment_form_md_info       : "Markdown je podporovaný."
+  comment_form_name_label    : "Meno"
+  comment_form_email_label   : "Emailová adresa"
+  comment_form_website_label : "Webstránka (voliteľné)"
+  comment_btn_submit         : "Vlož komentár"
+  comment_btn_submitted      : "Vložený"
+  comment_success_msg        : "Ďakujem za tvoj komentár! Po schválení bude zobrazený na stránke."
+  comment_error_msg          : "Prepáč, pri ukladaní nastala chyba. Ubezpeč sa prosím, že si vyplnil všetky požadované polia a skús znova."
+sk-SK:
+  <<: *DEFAULT_SK
+
+# Hungarian
+# -----------------
+hu: &DEFAULT_HU
+  comments_label             : "Szólj hozzá!"
+  comments_title             : "Hozzászólások"
+  comment_form_info          : "Az e-mail címed nem lesz publikus. A csillagozott mezők kitöltése kötelező"
+  comment_form_comment_label : "Hozzászólás"
+  comment_form_md_info       : "Támogatott formázási mód: Markdown"
+  comment_form_name_label    : "Név"
+  comment_form_email_label   : "Email cím"
+  comment_form_website_label : "Honlap (nem kötelező):"
+  comment_btn_submit         : "Hozzászólás elküldése"
+  comment_btn_submitted      : "Hozzászólás elküldve"
+  comment_success_msg        : "Köszönjük a Hozzászólást! A Hozzászólások csak előzetes moderáció után lesznek publikusak."
+  comment_error_msg          : "Hoppá, hiba történt a beküldés közben. Kérlek ellenőrizd hogy minden kötelező mező ki van-e töltve."
+hu-HU:
+  <<: *DEFAULT_HU
+
+# Romanian
+# -----------------
+ro: &DEFAULT_RO
+  comments_label             : "Lasă un comentariu"
+  comments_title             : "Comentarii"
+  comment_form_info          : "Adresa ta de email nu va fi făcută publică. Câmpurile marcate sunt obligatorii"
+  comment_form_comment_label : "Comentariu"
+  comment_form_md_info       : "Markdown este suportat."
+  comment_form_name_label    : "Nume"
+  comment_form_email_label   : "Adresă de email"
+  comment_form_website_label : "Site (opțional)"
+  comment_btn_submit         : "Trimite comentariul"
+  comment_btn_submitted      : "Trimis"
+  comment_success_msg        : "Mulțumesc pentru comentariu! Va apărea pe site în momentul în care va fi aprobat."
+  comment_error_msg          : "Scuze, este o problemă cu comentariul tău. Asigură-te că toate câmpurile obligatorii au fost completate și încearcă din nou."
+ro-RO:
+  <<: *DEFAULT_RO
+
+# Punjabi
+# -----------------
+pa: &DEFAULT_PA
+  comments_label             : "ਇੱਕ ਟਿੱਪਣੀ ਛੱਡੋ"
+  comments_title             : "ਟਿੱਪਣੀਆਂ"
+  comment_form_info          : "ਤੁਹਾਡਾ ਈਮੇਲ ਪਤਾ ਪ੍ਰਕਾਸ਼ਿਤ ਨਹੀਂ ਕੀਤਾ ਜਾਵੇਗਾ। ਅਨੁਮਾਨਿਤ ਸਥਾਨਾਂ ਨੂੰ ਅੰਡਰਲਾਈਨ ਕੀਤਾ ਗਿਆ ਹੈ"
+  comment_form_comment_label : "ਟਿੱਪਣੀ"
+  comment_form_md_info       : "ਮਾਰਕਡਾਊਨ ਵਰਤ ਸਕਦੇ ਹੋ।"
+  comment_form_name_label    : "ਨਾਮ"
+  comment_form_email_label   : "ਈਮੇਲ ਪਤਾ"
+  comment_form_website_label : "ਵੈਬਸਾਈਟ (ਵਿਕਲਪਿਕ)"
+  comment_btn_submit         : "ਕੋਈ ਟਿੱਪਣੀ ਭੇਜੋ"
+  comment_btn_submitted      : "ਪੇਸ਼ ਕੀਤਾ"
+  comment_success_msg        : "ਤੁਹਾਡੀਆਂ ਟਿੱਪਣੀਆਂ ਲਈ ਧੰਨਵਾਦ! ਇਹ ਮਨਜ਼ੂਰੀ ਮਿਲਣ ਦੇ ਬਾਅਦ ਸਾਈਟ 'ਤੇ ਦਿਖਾਇਆ ਜਾਵੇਗਾ।"
+  comment_error_msg          : "ਮੁਆਫ ਕਰਨਾ, ਤੁਹਾਡੀ ਅਧੀਨਗੀ ਵਿੱਚ ਕੋਈ ਗਲਤੀ ਹੋਈ ਸੀ ਕਿਰਪਾ ਕਰਕੇ ਯਕੀਨੀ ਬਣਾਓ ਕਿ ਸਾਰੇ ਲੋੜੀਂਦੇ ਖੇਤਰ ਪੂਰੇ ਹੋ ਗਏ ਹਨ ਅਤੇ ਦੁਬਾਰਾ ਕੋਸ਼ਿਸ਼ ਕਰੋ।"
+pa-IN:
+  <<: *DEFAULT_PA  
+
+# Another locale
+# --------------
+#

blog.bryanroessler.com/_includes/cloudflare_analytics.html

@@ -0,0 +1,8 @@
+{% if site.cloudflare_analytics %}
+<!-- Cloudflare Web Analytics -->
+<script defer
+    src='https://static.cloudflareinsights.com/beacon.min.js'
+    data-cf-beacon='{"token": "{{ site.cloudflare_analytics}}"}'>
+</script>
+<!-- End Cloudflare Web Analytics -->
+{% endif %}

blog.bryanroessler.com/_includes/commentbox.html

@@ -0,0 +1,7 @@
+{% if site.commentbox %}
+
+    <div class="commentbox"></div>
+    <script src="https://unpkg.com/commentbox.io/dist/commentBox.min.js"></script>
+    <script>commentBox('{{ site.commentbox }}')</script>
+
+{% endif %}

blog.bryanroessler.com/_includes/comments.html

@@ -0,0 +1,8 @@
+{% if page.comments %}
+  {% include disqus.html %}
+  {% include fb-comment.html %}
+  {% include staticman-comments.html %}
+  {% include utterances-comment.html %}
+  {% include giscus-comment.html %}
+  {% include commentbox.html %}
+{% endif %}

blog.bryanroessler.com/_includes/fb-comment.html

@@ -8,7 +8,7 @@
        js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.12&appId={{ site.fb_comment_id }}&autoLogAppEvents=1';
        fjs.parentNode.insertBefore(js, fjs);
     }(document, 'script', 'facebook-jssdk'));</script>
-    <div class="fb-comments" data-href="{{ site.url }}{{ page.url }}" data-width="100%" data-numposts="5"></div>
+    <div class="fb-comments" data-href="{{ page.url | absolute_url }}" data-width="100%" data-numposts="5"></div>
     <noscript>Please enable JavaScript to view the comments powered by Facebook.</noscript>
 </div>
 {%- endif -%}

blog.bryanroessler.com/_includes/footer-scripts.html

@@ -4,6 +4,21 @@
   {% endfor %}
 {% endif %}
 
+{% if layout.common-js %}
+  {% for js in layout.common-js %}
+    <!-- doing something a bit funky here because I want to be careful not to include JQuery twice! -->
+    {% if js contains 'jquery' %}
+      <script>
+      	if (typeof jQuery == 'undefined') {
+          document.write('<script src="{{ js | relative_url }}"></scr' + 'ipt>');
+      	}
+      </script>
+    {% else %}
+      <script src="{{ js | relative_url }}"></script>
+    {% endif %}
+  {% endfor %}
+{% endif %}
+
 {% if page.ext-js %}
   {% for js in page.ext-js %}
     {% include ext-js.html js=js %}
@@ -12,21 +27,6 @@
 
 {% if page.js %}
   {% for js in page.js %}
-	<script src="{{ js | prepend: site.baseurl | replace: '//', '/' }}"></script>
-  {% endfor %}
-{% endif %}
-
-{% if layout.common-js %}
-  {% for js in layout.common-js %}
-    <!-- doing something a bit funky here because I want to be careful not to include JQuery twice! -->
-    {% if js contains 'jquery' %}
-      <script>
-      	if (typeof jQuery == 'undefined') {
-      	  document.write('<script src="{{ js | prepend: site.baseurl | replace: "//", "/" }}"></scr' + 'ipt>');
-      	}
-      </script>
-    {% else %}
-	<script src="{{ js | prepend: site.baseurl | replace: '//', '/' }}"></script>
-    {% endif %}
+    <script src="{{ js | relative_url }}"></script>
   {% endfor %}
 {% endif %}

blog.bryanroessler.com/_includes/footer.html

@@ -8,7 +8,7 @@
             {%- assign element = site.data.SocialNetworks[curkey] -%}
             <li>
             {%- if curkey == 'rss' -%}
-              <a href="{{ '/feed.xml' | prepend: site.baseurl }}" title="{{ element.name }}">
+              <a href="{{ '/feed.xml' | relative_url }}" title="{{ element.name }}">
             {%- elsif curkey == 'yelp' -%}
               <a href="https://{{ site.social-network-links[curkey] }}.yelp.com" title="{{ element.name }}">
             {%- else -%}
@@ -30,7 +30,7 @@
 
       {% if site.url-pretty %}
       &nbsp;&bull;&nbsp;
-      <a href="{{ site.url }}">{{ site.url-pretty }}</a>
+      <a href="{{ '' | absolute_url }}">{{ site.url-pretty }}</a>
       {% endif %}
 
       {% if site.matomo %}
@@ -41,10 +41,10 @@
       {% endif%}
       </p>
           <!-- Please don't remove this, keep my open source work credited :) -->
-    <!--<p class="theme-by text-muted">
+    <p class="theme-by text-muted">
       Theme by
-      <a href="http://deanattali.com/beautiful-jekyll/">beautiful-jekyll</a>
-    </p>-->
+      <a href="https://deanattali.com/beautiful-jekyll/">beautiful-jekyll</a>
+    </p>
       </div>
     </div>
   </div>

blog.bryanroessler.com/_includes/giscus-comment.html

@@ -0,0 +1,16 @@
+{% if site.giscus.repository and site.giscus.hostname %}
+
+<script src="https://{{ site.giscus.hostname }}/client.js"
+        data-repo="{{ site.giscus.repository }}"
+        data-repo-id="{{ site.giscus.repository-id }}"
+        data-category="{{ site.giscus.category }}"
+        data-category-id="{{ site.giscus.category-id }}"
+        data-mapping="{{ site.giscus.mapping }}"
+        data-reactions-enabled="{{ site.giscus.reactions-enabled }}"
+        data-emit-metadata="{{ site.giscus.emit-metadata }}"
+        data-theme="{{ site.giscus.theme }}"
+        crossorigin="anonymous"
+        async>
+</script>
+
+{% endif %}

blog.bryanroessler.com/_includes/google_analytics.html

@@ -1,12 +1,14 @@
 {% if site.google_analytics %}
-	<!-- Google Analytics -->
-	<script>
-		(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
-		(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
-		m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
-		})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
+<!-- Google Analytics -->
+<script>
+    (function (i, s, o, g, r, a, m) {
+        i['GoogleAnalyticsObject'] = r; i[r] = i[r] || function () {
+            (i[r].q = i[r].q || []).push(arguments)
+        }, i[r].l = 1 * new Date(); a = s.createElement(o),
+            m = s.getElementsByTagName(o)[0]; a.async = 1; a.src = g; m.parentNode.insertBefore(a, m)
+    })(window, document, 'script', 'https://www.google-analytics.com/analytics.js', 'ga');
     ga('create', '{{ site.google_analytics }}', 'auto');
     ga('send', 'pageview');
-	</script>
-	<!-- End Google Analytics -->
+</script>
+<!-- End Google Analytics -->
 {% endif %}

blog.bryanroessler.com/_includes/gtag.html

@@ -0,0 +1,11 @@
+{% if site.gtag %}
+<!-- Global site tag (gtag.js) - Google Analytics -->
+<script async src="https://www.googletagmanager.com/gtag/js?id={{ site.gtag }}"></script>
+    <script>
+          window.dataLayer = window.dataLayer || [];
+  function gtag(){dataLayer.push(arguments);}
+  gtag('js', new Date());
+
+  gtag('config', '{{ site.gtag }}');
+</script>
+{% endif %}

blog.bryanroessler.com/_includes/head.html

@@ -1,7 +1,7 @@
 <head>
   <meta charset="utf-8" />
   <meta http-equiv="X-UA-Compatible" content="IE=edge">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, viewport-fit=cover">
 
   <title>{% if page.use-site-title %}{{ site.title }} {{ site.title-separator }} {{ site.description }}{% elsif page.title %}{{ page.title }}{% else %}{{ site.title }}{% endif %}</title>
 
@@ -11,8 +11,9 @@
   <meta name="description" content="{{ page.subtitle }}">
   {% endif %}
 
-  <link rel="alternate" type="application/rss+xml" title="{{ site.title }} {{ site.title-separator }} {{ site.description }}" href="{{ site.baseurl }}/feed.xml" />
+  <link rel="alternate" type="application/rss+xml" title="{{ site.title }} {{ site.title-separator }} {{ site.description }}" href="{{ '/feed.xml' | absolute_url }}" />
 
+  {% include gtag.html %}
   {% include gtm_head.html %}
   {% include google_analytics.html %}
 
@@ -24,7 +25,7 @@
 
   {% if layout.common-css %}
     {% for css in layout.common-css %}
-      <link rel="stylesheet" href="{{ css | prepend: site.baseurl | replace: '//', '/' }}" />
+      <link rel="stylesheet" href="{{ css | relative_url }}" />
     {% endfor %}
   {% endif %}
 
@@ -42,7 +43,7 @@
 
   {% if page.css %}
     {% for css in page.css %}
-      <link rel="stylesheet" href="{{ css | prepend: site.baseurl | replace: '//', '/' }}" />
+      <link rel="stylesheet" href="{{ css | relative_url }}" />
     {% endfor %}
   {% endif %}
 
@@ -77,17 +78,17 @@
   <meta property="og:type" content="website" />
 
   {% if page.id %}
-  <meta property="og:url" content="{{ site.url }}{{ page.url }}" />
-  <link rel="canonical" href="{{ site.url }}{{ page.url }}" />
+  <meta property="og:url" content="{{ page.url | absolute_url }}" />
+  <link rel="canonical" href="{{ page.url | absolute_url }}" />
   {% else %}
-  <meta property="og:url" content="{{ site.url }}{{ page.url | remove: '/index.html' | remove: '.html' }}" />
-  <link rel="canonical" href="{{ site.url }}{{ page.url | remove: '/index.html' | remove: '.html' }}" />
+  <meta property="og:url" content="{{ page.url | absolute_url | strip_index }}" />
+  <link rel="canonical" href="{{ page.url | absolute_url | strip_index }}" />
   {% endif %}
 
   {% if page.share-img %}
   <meta property="og:image" content="{{ page.share-img }}" />
   {% elsif site.avatar %}
-  <meta property="og:image" content="{{ site.url }}{{ site.avatar }}" />
+  <meta property="og:image" content="{{ site.avatar | absolute_url }}" />
   {% endif %}
 
 
@@ -115,11 +116,16 @@
   {% if page.share-img %}
   <meta name="twitter:image" content="{{ page.share-img }}" />
   {% elsif site.avatar %}
-  <meta name="twitter:image" content="{{ site.url }}{{ site.avatar }}" />
+  <meta name="twitter:image" content="{{ site.avatar | absolute_url }}" />
   {% endif %}
 
   {% if site.matomo %}
   {% include matomo.html %}
   {% endif %}
 
+  {% if page.comments and site.staticman.repository and site.staticman.branch %}
+  <!-- Staticman -->
+  <link rel="stylesheet" href="{{ "/css/staticman.css" | relative_url }}" />
+  {% endif %}
+
 </head>

blog.bryanroessler.com/_includes/header.html

@@ -8,10 +8,10 @@
 	  {% assign imgnum = forloop.index %}
 	  {% for imginfo in bigimg %}
 	    {% if imginfo[0] %}
-		  data-img-src-{{ imgnum }}="{{ imginfo[0] | prepend: site.baseurl | replace: '//', '/' }}"
+		  data-img-src-{{ imgnum }}="{{ imginfo[0] | relative_url }}"
 		  data-img-desc-{{ imgnum }}="{{ imginfo[1] }}"
 		{% else %}
-		  data-img-src-{{ imgnum }}="{{ imginfo | prepend: site.baseurl | replace: '//', '/' }}"
+		  data-img-src-{{ imgnum }}="{{ imginfo | relative_url }}"
 		{% endif %}
 	  {% endfor %}
     {% endfor %}
@@ -36,7 +36,7 @@
 		  {% endif %}
 
 		  {% if include.type == "post" %}
-		  <span class="post-meta">Posted on {{ page.date | date: "%B %-d, %Y" }}</span>
+		  <span class="post-meta">Posted on {{ page.date | date: site.date_format }}</span>
 		  {% endif %}
         </div>
       </div>
@@ -61,7 +61,7 @@
 		  {% endif %}
 
 		  {% if include.type == "post" %}
-		  <span class="post-meta">Posted on {{ page.date | date: "%B %-d, %Y" }}</span>
+		  <span class="post-meta">Posted on {{ page.date | date: site.date_format }}</span>
 		  {% endif %}
         </div>
       </div>

blog.bryanroessler.com/_includes/just_comments.html

@@ -0,0 +1,4 @@
+{%- if site.just-comments -%}
+<div class="just-comments" data-apikey="{{site.just-comments}}"></div>
+<script async src="https://just-comments.com/w2.js"></script>
+{%- endif -%}

blog.bryanroessler.com/_includes/mathjax.html

@@ -0,0 +1,12 @@
+{% if page.mathjax %}
+<script type="text/javascript">
+  MathJax = {
+    options: {
+      skipHtmlTags: [
+        'script', 'noscript', 'style', 'textarea', 'pre', 'code'
+      ]
+    }
+  };
+</script>
+<script type="text/javascript" async src="https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script>
+{% endif %}

blog.bryanroessler.com/_includes/nav.html

@@ -7,49 +7,47 @@
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
       </button>
-      {% if site.title-img %}
-        <a class="navbar-brand navbar-brand-logo" href="{{ site.url }}"><img src="{{ site.title-img }}"/></a>
-      {% else %}
-        <a class="navbar-brand" href="{{ site.url }}">{{ site.title }}</a>
-      {% endif %}
+      {%- if site.title-img -%}
+        <a class="navbar-brand navbar-brand-logo" href="{{ '' | absolute_url }}"><img src="{{ site.title-img }}"/></a>
+      {%- else -%}
+        <a class="navbar-brand" href="{{ '' | absolute_url }}">{{ site.title }}</a>
+      {%- endif -%}
     </div>
 
     <div class="collapse navbar-collapse" id="main-navbar">
       <ul class="nav navbar-nav navbar-right">
-      {% for link in site.navbar-links %}
-        {% if link[1].first %}
+      {%- for link in site.navbar-links -%}
+        {%- if link[1].first %}
           <li class="navlinks-container">
             <a class="navlinks-parent" href="javascript:void(0)">{{ link[0] }}</a>
             <div class="navlinks-children">
-              {% for childlink in link[1] %}
-                {% for linkparts in childlink %}
-                  {% include navbarlink.html link=linkparts %}
-                {% endfor %}
-              {% endfor %}
+              {%- for childlink in link[1] -%}
+              {%- for linkparts in childlink %}
+              <a href="{{ linkparts[1] | relative_url }}">{{ linkparts[0] }}</a>
+              {%- endfor -%}
+              {%- endfor %}
             </div>
           </li>
         {% else %}
-          <li>
-            {% include navbarlink.html link=link %}
-          </li>
-        {% endif %}
-        {% endfor %}
+          <li><a href="{{ link[1] | relative_url }}">{{ link[0] }}</a></li>
+        {%- endif -%}
+      {%- endfor -%}
       </ul>
     </div>
 
 	{% if page.image and (layout.show-avatar or page.show-avatar) %}
 	<div class="avatar-container">
 	  <div class="avatar-img-border">
-	    <a href="{{ site.url }}">
-	      <img class="avatar-img" src="{{ page.image | prepend: site.baseurl | replace: '//', '/' }}" />
+	    <a href="{{ '' | absolute_url }}">
+	      <img class="avatar-img" src="{{ page.image | relative_url }}" />
 		</a>
 	  </div>
 	</div>
 	{% elsif site.avatar and (layout.show-avatar or page.show-avatar) %}
 	<div class="avatar-container">
 	  <div class="avatar-img-border">
-	    <a href="{{ site.url }} ">
-	      <img class="avatar-img" src="{{ site.avatar | prepend: site.baseurl | replace: '//', '/' }}" />
+	    <a href="{{ '' | absolute_url }}">
+	      <img class="avatar-img" src="{{ site.avatar | relative_url }}" />
 		</a>
 	  </div>
 	</div>

blog.bryanroessler.com/_includes/readtime.html

@@ -0,0 +1,16 @@
+<!--- "ReadTime on GitHub Jekyll" (c) 2020 Ruby Griffith Ramirez, MIT License -->
+
+{% assign ReadTime = page.content | strip_html | number_of_words %}
+{% assign calcReadTime = ReadTime | float %}
+{% assign finalReadTime = calcReadTime | divided_by:200 | round: 2 %}
+{% assign number = finalReadTime | round %}
+{% if number >= 1 %}
+  {% assign yesReadTime = number | append: " minute read" %}
+  <span class="post-meta"><span class="d-none d-md-inline middot">&middot;</span> {{ yesReadTime }}</span>
+{% elsif number < 1 %}
+  {% assign minReadTime = '&lt; 1 minute read' %}
+  <span class="post-meta"><span class="d-none d-md-inline middot">&middot;</span> {{ minReadTime }}</span>
+{% else %}
+  {% assign nilReadTime = number | replace:'0',' ' %}
+  {{ nilReadTime }}
+{% endif %}

blog.bryanroessler.com/_includes/search.html

@@ -0,0 +1,19 @@
+{% if site.post_search %}
+
+<div id="beautifuljekyll-search-overlay">
+
+  <div id="nav-search-exit" title="Exit search">✕</div>
+  <input type="text" id="nav-search-input" placeholder="Search">
+  <ul id="search-results-container"></ul>
+  
+  <script src="https://unpkg.com/simple-jekyll-search@latest/dest/simple-jekyll-search.min.js"></script>
+  <script>
+    SimpleJekyllSearch({
+      searchInput: document.getElementById('nav-search-input'),
+      resultsContainer: document.getElementById('search-results-container'),
+      json: '{{ site.baseurl }}/assets/data/searchcorpus.json' 
+    });
+  </script>
+</div>
+
+{% endif %}

blog.bryanroessler.com/_includes/social-networks-links.html

@@ -0,0 +1,401 @@
+{% if site.social-network-links %}
+<ul class="list-inline text-center footer-links">
+
+{%- for network in site.social-network-links -%}
+
+  {%- if network[0] == "rss" and network[1] and site.rss-description -%}
+  <li class="list-inline-item">
+    <a href="{{ '/feed.xml' | relative_url }}" title="RSS">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-rss fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">RSS</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "email" -%}
+  <li class="list-inline-item">
+    <a href="mailto:{{ network[1] }}" title="Email me">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-envelope fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Email me</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "calendly" -%}
+  <li class="list-inline-item">
+    <a href="https://calendly.com/{{ network[1] }}" title="Schedule a meeting with me">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-calendar-check fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Schedule a meeting with me</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "facebook" -%}
+  <li class="list-inline-item">
+    <a href="https://www.facebook.com/{{ network[1] }}" title="Facebook">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-facebook fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Facebook</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "telegram" -%}
+  <li class="list-inline-item">
+    <a href="https://t.me/{{ network[1] }}" title="Telegram">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-telegram-plane fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Telegram</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "whatsapp" -%}
+  <li class="list-inline-item">
+    <a href="https://wa.me/{{ network[1] }}" title="Whatsapp">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-whatsapp fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Whatsapp</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "github" -%}
+  <li class="list-inline-item">
+    <a href="https://github.com/{{ network[1] }}" title="GitHub">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-github fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">GitHub</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "gitlab" -%}
+  <li class="list-inline-item">
+    <a href="https://gitlab.com/{{ network[1] }}" title="GitLab">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-gitlab fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">GitLab</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "twitter" -%}
+  <li class="list-inline-item">
+    <a href="https://twitter.com/{{ network[1] }}" title="X (Twitter)">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-x-twitter fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">X (Twitter)</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "reddit" -%}
+  {% assign reddit_start = network[1] | split: "/" | first -%}
+  {% unless reddit_start == 'r' or reddit_start == 'u' -%}
+    {% assign reddit_url_prefix = 'u/' -%}
+  {% endunless -%}
+  <li class="list-inline-item">
+    <a href="https://reddit.com/{{ reddit_url_prefix }}{{ network[1] }}" title="Reddit">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-reddit fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Reddit</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "linkedin" -%}
+  <li class="list-inline-item">
+    <a href="https://linkedin.com/in/{{ network[1] }}" title="LinkedIn">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-linkedin fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">LinkedIn</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "xing" -%}
+  <li class="list-inline-item">
+    <a href="https://www.xing.com/profile/{{ network[1] }}" title="Xing">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-xing fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Xing</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "stackoverflow" -%}
+  <li class="list-inline-item">
+    <a href="https://stackoverflow.com/users/{{ network[1] }}" title="StackOverflow">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-stack-overflow fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">StackOverflow</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "snapchat" -%}
+  <li class="list-inline-item">
+    <a href="https://www.snapchat.com/add/{{ network[1] }}" title="Snapchat">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-snapchat-ghost fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Snapchat</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "instagram" -%}
+  <li class="list-inline-item">
+    <a href="https://www.instagram.com/{{ network[1] }}" title="Instagram">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-instagram fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Instagram</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "youtube" -%}
+  <li class="list-inline-item">
+    <a href="https://www.youtube.com/{{ network[1] }}" title="YouTube">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-youtube fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">YouTube</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "spotify" -%}
+  <li class="list-inline-item">
+    <a href="https://open.spotify.com/user/{{ network[1] }}" title="Spotify">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-spotify fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Spotify</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "telephone" -%}
+  <li class="list-inline-item">
+    <a href="tel:{{ network[1] }}" title="Phone">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-phone fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Phone</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "steam" -%}
+  <li class="list-inline-item">
+    <a href="https://steamcommunity.com/id/{{ network[1] }}" title="Steam">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-steam fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Steam</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "twitch" -%}
+  <li class="list-inline-item">
+    <a href="https://www.twitch.tv/{{ network[1] }}" title="Twitch">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-twitch fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Twitch</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "yelp" -%}
+  <li class="list-inline-item">
+    <a href="https://yelp.com/{{ network[1] }}" title="Yelp">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-yelp fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Yelp</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "mastodon" -%}
+  <li class="list-inline-item">
+    <a rel="me" href="https://{{ network[1] }}" title="Mastodon">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-mastodon fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Mastodon</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "bluesky" -%}
+  <li class="list-inline-item">
+    <a rel="me" href="https://bsky.app/profile/{{ network[1] }}" title="Bluesky">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-square fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Bluesky</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "ORCID" -%}
+ <li class="list-inline-item">
+   <a href="https://orcid.org/{{ network[1] }}" title="ORCID">
+     <span class="fa-stack fa-lg" aria-hidden="true">
+       <i class="fas fa-circle fa-stack-2x"></i>
+       <i class="fab fa-orcid fa-stack-1x fa-inverse"></i>
+     </span>
+     <span class="sr-only">ORCID</span>
+   </a>
+ </li>
+  {%- endif -%}
+
+  {%- if network[0] == "google-scholar" -%}
+  <li class="list-inline-item">
+    <a href="https://scholar.google.com/citations?user={{ network[1] }}" title="Google Scholar">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fa fa-graduation-cap fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Google Scholar</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "patreon" -%}
+  <li class="list-inline-item">
+    <a href="https://patreon.com/{{ network[1] }}" title="Patreon">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-patreon fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Patreon</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "medium" -%}
+  <li class="list-inline-item">
+    <a href="https://medium.com/@{{ network[1] }}" title="Medium">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-medium fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Medium</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "itchio" -%}
+  <li class="list-inline-item">
+    <a href="https://{{ network[1] }}.itch.io/" title="Itchio">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-itch-io fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Itchio</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "discord" -%}
+  {% assign discord_start = network[1] | split: "/" | first -%}
+  {% unless discord_start == 'users' or discord_start == 'invite' -%}
+    {% assign discord_url_prefix = 'invite/' -%}
+  {% endunless -%}
+  <li class="list-inline-item">
+    <a href="https://discord.com/{{discord_url_prefix}}{{network[1]}}" title="Discord">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-discord fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Discord</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "kaggle" -%}
+  <li class="list-inline-item">
+    <a href="https://www.kaggle.com/{{ network[1] }}" title="Kaggle">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-kaggle fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Kaggle</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "hackerrank" -%}
+  <li class="list-inline-item">
+    <a href="https://www.hackerrank.com/{{ network[1] }}" title="Hackerrank">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-hackerrank fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Hackerrank</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "untappd" -%}
+  <li class="list-inline-item">
+    <a href="https://untappd.com/user/{{ network[1] }}" title="Untappd">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-untappd fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Untappd</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+{%- endfor -%}
+
+</ul>
+{% endif %}

blog.bryanroessler.com/_includes/social-share.html

@@ -12,7 +12,7 @@
 
   {% if site.share-links-active.twitter %}
   <!--- Share on Twitter -->
-    <a href="https://twitter.com/intent/tweet?text={{ page.title | url_encode }}+{{ site.url }}{{ page.url }}"
+    <a href="https://twitter.com/intent/tweet?text={{ page.title | url_encode }}&url={{ page.url | absolute_url | url_encode }}"
       class="btn btn-social-icon btn-twitter" title="Share on Twitter">
       <span class="fa fa-fw fa-twitter" aria-hidden="true"></span>
       <span class="sr-only">Twitter</span>
@@ -21,25 +21,16 @@
 
   {% if site.share-links-active.facebook %}
   <!--- Share on Facebook -->
-    <a href="https://www.facebook.com/sharer/sharer.php?u={{ site.url }}{{ page.url }}"
+    <a href="https://www.facebook.com/sharer/sharer.php?u={{ page.url | absolute_url | url_encode }}"
       class="btn btn-social-icon btn-facebook" title="Share on Facebook">
       <span class="fa fa-fw fa-facebook" aria-hidden="true"></span>
       <span class="sr-only">Facebook</span>
     </a>
   {% endif %}
 
-  {% if site.share-links-active.google %}
-  <!--- Share on Google Plus -->
-    <a href="https://plus.google.com/share?url={{ site.url }}{{ page.url }}"
-      class="btn btn-social-icon btn-google" title="Share on Google+">
-      <span class="fa fa-fw fa-google-plus" aria-hidden="true"></span>
-      <span class="sr-only">Google+</span>
-    </a>
-  {% endif %}
-
   {% if site.share-links-active.linkedin %}
   <!--- Share on LinkedIn -->
-    <a href="https://www.linkedin.com/shareArticle?mini=true&url={{ site.url }}{{ page.url }}"
+    <a href="https://www.linkedin.com/shareArticle?mini=true&url={{ page.url | absolute_url | url_encode }}"
       class="btn btn-social-icon btn-linkedin" title="Share on LinkedIn">
       <span class="fa fa-fw fa-linkedin" aria-hidden="true"></span>
       <span class="sr-only">LinkedIn</span>

blog.bryanroessler.com/_includes/staticman-comment.html

@@ -0,0 +1,22 @@
+<article id="comment{{ include.index }}" class="js-comment comment" itemprop="comment" itemscope itemtype="https://schema.org/Comment">
+  <div class="comment__avatar-wrapper">
+    <img class="comment__avatar" src="https://www.gravatar.com/avatar/{{ include.email }}?d=mm&s=80" alt="{{ include.name }}">
+  </div>
+  <div class="comment__content-wrapper">
+    <h4 class="comment__author" itemprop="author" itemscope itemtype="https://schema.org/Person">
+      {% unless include.url == blank %}
+        <span itemprop="name"><a rel="external nofollow" itemprop="url" href="{{ include.url }}">{{ include.name }}</a></span>
+      {% else %}
+        <span itemprop="name">{{ include.name }}</span>
+      {% endunless %}
+    </h4>
+    <p class="comment__date">
+      {% if include.date %}
+        {% if include.index %}<a href="#comment{{ include.index }}" itemprop="url">{% endif %}
+        <time datetime="{{ include.date | date_to_xmlschema }}" itemprop="datePublished">{{ include.date | date: "%B %d, %Y at %I:%M %p" }}</time>
+        {% if include.index %}</a>{% endif %}
+      {% endif %}
+    </p>
+    <div itemprop="text">{{ include.message | markdownify }}</div>
+  </div>
+</article>

blog.bryanroessler.com/_includes/staticman-comments.html

@@ -0,0 +1,81 @@
+{% if site.staticman.repository and site.staticman.branch %}
+  <div class="page__comments">
+    <!-- Start static comments -->
+    <div class="js-comments">
+      {% if site.data.comments[page.slug] %}
+        <h3 class="page__comments-title">{{ site.data.ui-text[site.locale].comments_title | default: "Comments" }}</h3>
+        {% assign comments = site.data.comments[page.slug] | sort %}
+        {% for comment in comments %}
+          {% assign email = comment[1].email %}
+          {% assign name = comment[1].name %}
+          {% assign url = comment[1].url %}
+          {% assign date = comment[1].date %}
+          {% assign message = comment[1].message %}
+          {% include staticman-comment.html index=forloop.index email=email name=name url=url date=date message=message %}
+        {% endfor %}
+      {% endif %}
+    </div>
+    <!-- End static comments -->
+    <!-- Start new comment form -->
+    <div class="page__comments-form">
+      <h3 class="page__comments-title">{{ site.data.ui-text[site.locale].comments_label | default: "Leave a Comment" }}</h3>
+      <p class="small">{{ site.data.ui-text[site.locale].comment_form_info | default: "Your email address will not be published. Required fields are marked" }} <span class="required">*</span></p>
+      <form id="new_comment" class="page__comments-form js-form form" method="post">
+        <div class="form-group">
+          <label for="comment-form-message">{{ site.data.ui-text[site.locale].comment_form_comment_label | default: "Comment" }} <small class="required">*</small></label><br>
+          <textarea type="text" rows="12" cols="36" id="comment-form-message" name="fields[message]" tabindex="1"></textarea>
+          <div class="small help-block"><a href="https://daringfireball.net/projects/markdown/">{{ site.data.ui-text[site.locale].comment_form_md_info | default: "Markdown is supported." }}</a></div>
+        </div>
+        <div class="form-group">
+          <label for="comment-form-name">{{ site.data.ui-text[site.locale].comment_form_name_label | default: "Name" }} <small class="required">*</small></label>
+          <input type="text" id="comment-form-name" name="fields[name]" tabindex="2" />
+        </div>
+        <div class="form-group">
+          <label for="comment-form-email">{{ site.data.ui-text[site.locale].comment_form_email_label | default: "Email address" }} <small class="required">*</small></label>
+          <input type="email" id="comment-form-email" name="fields[email]" tabindex="3" />
+        </div>
+        <div class="form-group">
+          <label for="comment-form-url">{{ site.data.ui-text[site.locale].comment_form_website_label | default: "Website (optional)" }}</label>
+          <input type="url" id="comment-form-url" name="fields[url]" tabindex="4"/>
+        </div>
+        <div class="form-group hidden" style="display: none;">
+          <input type="hidden" name="options[origin]" value="{{ page.url | absolute_url }}">
+          <input type="hidden" name="options[slug]" value="{{ page.slug }}">
+          <label for="comment-form-location">Not used. Leave blank if you are a human.</label>
+          <input type="text" id="comment-form-location" name="fields[hidden]" autocomplete="off"/>
+          {% if site.staticman.reCaptcha.siteKey %}<input type="hidden" name="options[reCaptcha][siteKey]" value="{{ site.staticman.reCaptcha.siteKey }}">{% endif %}
+          {% if site.staticman.reCaptcha.secret %}<input type="hidden" name="options[reCaptcha][secret]" value="{{ site.staticman.reCaptcha.secret }}">{% endif %}
+        </div>
+        <!-- Start comment form alert messaging -->
+        <p class="hidden js-notice">
+          <strong class="js-notice-text-success hidden">{{ site.data.ui-text[site.locale].comment_success_msg | default: "Thanks for your comment! It will show on the site once it has been approved." }}</strong>
+          <strong class="js-notice-text-failure hidden">{{ site.data.ui-text[site.locale].comment_error_msg | default: "Sorry, there was an error with your submission. Please make sure all required fields have been completed and try again." }}</strong>
+        </p>
+        <!-- End comment form alert messaging -->
+        {% if site.staticman.reCaptcha.siteKey %}
+          <div class="form-group">
+            <div class="g-recaptcha" data-sitekey="{{ site.staticman.reCaptcha.siteKey }}"></div>
+          </div>
+        {% endif %}
+        <div class="form-group">
+          <button type="submit" id="comment-form-submit" tabindex="5" class="btn btn--primary btn--large">{{ site.data.ui-text[site.locale].comment_btn_submit | default: "Submit Comment" }}</button>
+          <button type="submit" id="comment-form-submitted" tabindex="5" class="btn btn--primary btn--large hidden" disabled>{{ site.data.ui-text[site.locale].comment_btn_submitted | default: "Submitted" }}</button>
+        </div>
+      </form>
+    </div>
+    <!-- End new comment form -->
+    <!-- Load reCaptcha if site key is set -->
+    {% if site.staticman.reCaptcha.siteKey %}
+      <script async src="https://www.google.com/recaptcha/api.js"></script>
+    {% endif %}
+  </div>
+
+  <!-- Load script to handle comment form submission -->
+  <!-- doing something a bit funky here because I want to be careful not to include JQuery twice! -->
+  <script>
+    if (typeof jQuery == 'undefined') {
+      document.write('<script src="{{ "/js/jquery-1.11.2.min.js" | relative_url }}"></scr' + 'ipt>');
+    }
+  </script>
+  <script src="{{ "/js/staticman.js" | relative_url }}"></script>
+{% endif %}

blog.bryanroessler.com/_includes/utterances-comment.html

@@ -0,0 +1,13 @@
+{% if site.utterances.repository and site.utterances.issue-term  %}
+
+<script src="https://utteranc.es/client.js"
+        repo="{{ site.utterances.repository }}"
+        issue-term="{{ site.utterances.issue-term }}"
+        theme="{{ site.utterances.theme}}"
+        label="{{ site.utterances.label}}"
+        crossorigin="anonymous"
+        async>
+</script>
+
+{% endif %}
+

blog.bryanroessler.com/_layouts/home.html

@@ -0,0 +1,122 @@
+---
+layout: page
+---
+
+{{ content }}
+
+{% assign posts = paginator.posts | default: site.posts %}
+
+<!-- role="list" needed so that `list-style: none` in Safari doesn't remove the list semantics -->
+<ul class="posts-list list-unstyled" role="list">
+  {% for post in posts %}
+  <li class="post-preview">
+    <article>
+
+      {%- capture thumbnail -%}
+        {% if post.thumbnail-img %}
+          {{ post.thumbnail-img }}
+        {% elsif post.cover-img %}
+          {% if post.cover-img.first %}
+            {{ post.cover-img[0].first.first }}
+          {% else %}
+            {{ post.cover-img }}
+          {% endif %}
+        {% else %}
+        {% endif %}
+      {% endcapture %}
+      {% assign thumbnail=thumbnail | strip %}
+
+      {% if site.feed_show_excerpt == false %}
+      {% if thumbnail != "" %}
+      <div class="post-image post-image-normal">
+        <a href="{{ post.url | absolute_url }}" aria-label="Thumbnail">
+          <img src="{{ thumbnail | absolute_url }}" alt="Post thumbnail">
+        </a>
+      </div>
+      {% endif %}
+      {% endif %}
+
+      <a href="{{ post.url | absolute_url }}">
+        <h2 class="post-title">{{ post.title | strip_html }}</h2>
+
+        {% if post.subtitle %}
+          <h3 class="post-subtitle">
+          {{ post.subtitle | strip_html }}
+          </h3>
+        {% endif %}
+      </a>
+
+      {% if post.author %}
+        <span>By <strong>{{ post.author | strip_html }}</strong></span>
+      {% endif %}
+      <p class="post-meta">
+        {% assign date_format = site.date_format | default: "%B %-d, %Y" %}
+        Posted on {{ post.date | date: date_format }}
+      </p>
+
+      {% if thumbnail != "" %}
+      <div class="post-image post-image-small">
+        <a href="{{ post.url | absolute_url }}" aria-label="Thumbnail">
+          <img src="{{ thumbnail | absolute_url }}" alt="Post thumbnail">
+        </a>
+      </div>
+      {% endif %}
+
+      {% unless site.feed_show_excerpt == false %}
+      {% if thumbnail != "" %}
+      <div class="post-image post-image-short">
+        <a href="{{ post.url | absolute_url }}" aria-label="Thumbnail">
+          <img src="{{ thumbnail | absolute_url }}" alt="Post thumbnail">
+        </a>
+      </div>
+      {% endif %}
+
+      <div class="post-entry">
+        {% assign excerpt_length = site.excerpt_length | default: 50 %}
+        {{ post.excerpt | strip_html | truncatewords: excerpt_length }}
+        {% assign excerpt_word_count = post.excerpt | number_of_words %}
+        {% if post.content != post.excerpt or excerpt_word_count > excerpt_length %}
+          <a href="{{ post.url | absolute_url }}" class="post-read-more">[Read&nbsp;More]</a>
+        {% endif %}
+      </div>
+      {% endunless %}
+
+      {% if site.feed_show_tags != false and post.tags.size > 0 %}
+      <div class="blog-tags">
+        <span>Tags:</span>
+        <!-- role="list" needed so that `list-style: none` in Safari doesn't remove the list semantics -->
+        <ul class="d-inline list-inline" role="list">
+          {% for tag in post.tags %}
+          <li class="list-inline-item">
+            <a href="{{ '/tags' | absolute_url }}#{{- tag -}}">{{- tag -}}</a>
+          </li>
+          {% endfor %}
+        </ul>
+      </div>
+      {% endif %}
+
+    </article>
+  </li>
+  {% endfor %}
+</ul>
+
+{% if paginator.total_pages > 1 %}
+<ul class="pagination main-pager">
+  {% if paginator.previous_page %}
+  <li class="page-item previous">
+    <a class="page-link" href="{{ paginator.previous_page_path | absolute_url }}">
+      <i class="fas fa-arrow-left" alt="Newer Posts"></i>
+      <span class="d-none d-sm-inline-block">Newer Posts</span>
+    </a>
+  </li>
+  {% endif %}
+  {% if paginator.next_page %}
+  <li class="page-item next">
+    <a class="page-link" href="{{ paginator.next_page_path | absolute_url }}">
+      <span class="d-none d-sm-inline-block">Older Posts</span>
+      <i class="fas fa-arrow-right" alt="Older Posts"></i>
+    </a>
+  </li>
+  {% endif %}
+</ul>
+{% endif %}

blog.bryanroessler.com/_layouts/page.html

@@ -13,6 +13,12 @@ layout: base
 	        {% include disqus.html %}
         </div>
 	        {% include fb-comment.html %}
+        <div class="staticman-comments">
+          {% include staticman-comments.html %}
+        </div>
+        <div class="justcomments-comments">
+          {% include just_comments.html %}
+        </div>
 	    {% endif %}
     </div>
   </div>

blog.bryanroessler.com/_layouts/post.html

@@ -40,7 +40,7 @@ layout: base
           Tags:
           {% if site.link-tags %}
           {% for tag in page.tags %}
-            <a href="{{ site.baseurl }}/tags#{{- tag -}}">{{- tag -}}</a>
+            <a href="{{ '/tags' | relative_url }}#{{- tag -}}">{{- tag -}}</a>
           {% endfor %}
           {% else %}
             {{ page.tags | join: ", " }}
@@ -55,12 +55,12 @@ layout: base
       <ul class="pager blog-pager">
         {% if page.previous.url %}
         <li class="previous">
-          <a href="{{ page.previous.url | prepend: site.baseurl | replace: '//', '/' }}" data-toggle="tooltip" data-placement="top" title="{{page.previous.title}}">&larr; Previous Post</a>
+          <a href="{{ page.previous.url | relative_url }}" data-toggle="tooltip" data-placement="top" title="{{page.previous.title}}">&larr; Previous Post</a>
         </li>
         {% endif %}
         {% if page.next.url %}
         <li class="next">
-          <a href="{{ page.next.url | prepend: site.baseurl | replace: '//', '/' }}" data-toggle="tooltip" data-placement="top" title="{{page.next.title}}">Next Post &rarr;</a>
+          <a href="{{ page.next.url | relative_url }}" data-toggle="tooltip" data-placement="top" title="{{page.next.title}}">Next Post &rarr;</a>
         </li>
         {% endif %}
       </ul>
@@ -70,6 +70,12 @@ layout: base
           {% include disqus.html %}
         </div>
           {% include fb-comment.html %}
+        <div class="staticman-comments">
+          {% include staticman-comments.html %}
+        </div>
+        <div class="justcomments-comments">
+          {% include just_comments.html %}
+        </div>
       {% endif %}
     </div>
   </div>

blog.bryanroessler.com/_plugins/insert_git_code.rb

@@ -0,0 +1,21 @@
+require 'open-uri'
+
+module Jekyll
+    class InsertGitCode < Liquid::Tag
+
+        def initialize(tag_name, url, tokens)
+            super
+            url = url.strip()
+            @filename = File.basename(url)
+            encoded_url = URI.encode(url)
+            @file = URI.parse(encoded_url).read
+        end
+
+        def render(_context)
+            @file
+        end
+
+    end
+end
+
+Liquid::Template.register_tag('insert_git_code', Jekyll::InsertGitCode)

blog.bryanroessler.com/_posts/2018-06-22-strategies-for-maximizing-vps.md

@@ -11,18 +11,23 @@ The rapidly deflating prices of cloud storage (and other low-end) VPS services m
 VPS deal aggregate sites, such as [lowendbox](lowendbox.com), regularly provide offers on storage VPS services that rival shared web hosting or dedicated cloud backup providers. However, while the costs of cloud storage space have dropped dramatically, the CPU and memory configurations offered with the most storage VPS configurations are usually quite limited. Oftentimes a VPS provider will limit virtualized storage VPS instances to only 1 CPU core and <1GB memory (512MB is also common), since the intended use case is to simply provide enough resources for effective backup and retrieval.
 
 ### Selecting an OS
+
 For the purposes of minimizing RAM consumption on a low-end VPS, it is imperative to select an OS  that is lightweight, flexible, well-supported, and capable of running your intended services. Unfortunately, while most compute VPS instances provide a seemingly endless selection of server OSes to choose from, choices are usually limited on storage VPS instances by comparison. Windows Server is not a great choice because of its large memory footprint compared to its Linux-based equivalents. **Ubuntu Server LTS, CentOS, or Debian are usually safe bets**, but make sure to check that any third-party software (_i.e._ not in the repositories) that you intend to run are compatible with the libraries that ship with your Linux distribution of choice. The most common problem is trying to use newer software on older, stable Linux distributions. For example, [JRiver Media Center](https://yabb.jriver.com/interact/index.php/board,58.0.html) is built on Debian 8 Jessie but will not run on CentOS 7 because it ships with older C++ libraries. I prefer Redhat distributions (for reasons I will explain in a later post) but [my storage VPS host](www.time4vps.com) does not offer Fedora as an option (likely due to its short release cycle), which meant that my choices were limited to either Ubuntu 16.04 LTS or Debian 8. Expect for a base Linux OS installation to use ~125MB of RAM.
 
 ### Selecting a web server
+
 [Digital Ocean](https://www.digitalocean.com/community/tutorials/apache-vs-nginx-practical-considerations) offers an in-depth comparison of the two major web servers, Apache and Nginx. Long story short, **Nginx provides better performance and uses fewer resources than Apache** thanks to its asynchronous design. The Nginx process itself is single-threaded, which is perfect for a low-end VPS with only a single CPU core. Nginx can also be used as a [reverse proxy](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/) (using the `proxy_pass` block) to act as a secure front-end for other web services.
 
 ### Selecting a website generator
+
 In the past, web development for the layman necessitated using heavy content management systems like [Wordpress](wordpress.com) to handle website design and editing. Unfortunately, **a single instance of Wordpress can easily use up >256MB of RAM**, which would quickly gobble up the available resources on a low-end VPS. Additionally, Wordpress creates dynamic sites that chew up CPU cycles on the server to serve dynamic content whenever the site is accessed. Luckily there has recently been a shift among (primarily smaller) sites to using static site generators such as [**Jekyll**](https://jekyllrb.com/) (my favorite) or [HUGO](https://gohugo.io/) that compile sites beforehand and only serve static HTML/CSS versions of the page. This results in much lower overhead and resources, since post-compile there is nothing actually running except your web server (of course your OS may cache the site in memory to speed up future accesses).
 
 It's certainly possible to generate your sites locally and only transfer the output to your server's /www directory. However, since content creation in Jekyll is primarily some variation of Markdown language, I prefer using **Git** to push to the server and using post-hooks to generate the site remotely. It only takes a few seconds to generate most sites and as a result your source content is safely duplicated and version controlled on the storage VPS (that is the point of using a storage VPS in the first place, _right_?). As an alternative to git post-hooks (and for a slightly higher performance overhead), you can also use Jekyll's `--incremental` and `--watch` switches to easily and automatically regenerate selected site folders.
 
 ### Additional Services
+
 In addition to a lightweight web server, consider adding the following useful services:
+
 * Private Dynamic DNS
   * Use [MiniDynDNS](https://github.com/arkanis/minidyndns) to listen for IP address updates from your other computers (running a dynamic DNS client).
 * File syncing

blog.bryanroessler.com/_posts/2018-12-03-deploying-multiple-jekyll-sites.md

@@ -8,11 +8,12 @@ tags: [jekyll, git]
 
 As advertised, Jekyll is an excellent choice for building a simple (and secure!) personal or small business website. However, when compared to its better-known and bigger brethren, scaling the Jekyll workflow to manage multiple sites or subdomains is not readily apparent. In this post I will outline a git-based workflow to build and deploy a website with multiple subdomains.
 
-I prefer storing my work in version controlled git repositories in order to keep track of modifications and to assist in the backup and restore of my environment and data on multiple machines. One of the machines that I use to store this data [is also the cloud storage VPS that I use to run this site.]({{ site.baseurl }}{% post_url 2018-06-22-strategies-for-maximizing-vps %}) The storage VPS holds the [bare website repositories](https://git.bryanroessler.com/bryan/www) that I can push to and pull from my other development machines. Since my website repositories contain jekyll site code, all that I need to do is to instruct the VPS to build and deploy that code!
+I prefer storing my work in version controlled git repositories in order to keep track of modifications and to assist in the backup and restore of my environment and data on multiple machines. One of the machines that I use to store this data [is also the cloud storage VPS that I use to run this site.]({% post_url 2018-06-22-strategies-for-maximizing-vps %}) The storage VPS holds the [bare website repositories](https://git.bryanroessler.com/bryan/www) that I can push to and pull from my other development machines. Since my website repositories contain jekyll site code, all that I need to do is to instruct the VPS to build and deploy that code!
 
 There are three steps that need to occur for this to happen seamlessly after the git repos have been created (which is outside the scope of this post).
 
 On the client:
+
 1. Push website changes to the server
 
 On the server:
@@ -29,18 +30,19 @@ For larger websites, I prefer using nested git repositories to simplify website
 By combining the subgit strategy with some structured naming conventions it is possible to push, build, and deploy multiple subdomains or sites using a single git push from the client!
 
 Example:
-~~~
+
+~~~bash
 #!/usr/bin/env bash
 "/var/lib/git/gogs/gogs" hook --config='/var/lib/git/gogs/conf/app.ini' post-receive
 
 GIT_DIR="$(pwd)"
 TMP_GIT_DIR="/tmp/${GIT_DIR##*/}"
 
-if [ ! -d "${TMP_GIT_DIR}" ]; then
+if [[ ! -d "${TMP_GIT_DIR}" ]]; then
     git clone "${GIT_DIR}" "${TMP_GIT_DIR}"
-    cd "${TMP_GIT_DIR}"
+    cd "${TMP_GIT_DIR}" || exit $?
 else
-    cd "${TMP_GIT_DIR}"
+    cd "${TMP_GIT_DIR}" || exit $?
     unset GIT_DIR
     git fetch --all
     git reset --hard origin/master
@@ -48,12 +50,18 @@ else
 fi
 
 for site in *.*/; do
-  [ ! -d /var/www/${site} ] && mkdir -p /var/www/${site} && chgrp -R /var/www/${site} && chmod g+s /var/www/${site}
-  pushd ${site}
-  bundle install --deployment
-  bundle exec jekyll build --destination /var/www/${site}
-  popd
+    deploy_dir="/var/www/${site}"
+    if [[ ! -d "$deploy_dir" ]]; then
+        mkdir -p "$deploy_dir"
+        chgrp -R "$deploy_dir"
+        chmod g+s "$deploy_dir"
+    fi
+    pushd "${site}" || exit $?
+    ruby -S bundle install --deployment
+    ruby -S bundle exec jekyll build --destination "$deploy_dir"
+    popd || exit $?
 done
 
-exit
+exit 0
+
 ~~~

blog.bryanroessler.com/_posts/2019-02-09-automatic-certbot-namecheap-acme-dns.md

@@ -0,0 +1,177 @@
+---
+layout: post
+title: Autorenewing wildcard LetsEncrypt certificates on Namecheap using certbot + acme-dns
+subtitle: The "less" painful way
+#bigimg: /img/path.jpg
+tags: [certbot, acme-dns]
+---
+
+In early 2018, [Let's Encrypt](https://letsencrypt.org/) began issuing wildcard HTTPS certificates (e.g. for \*.bryanroessler.com), which vastly simplified the process of securing multi-domain personal websites for free. The main drawback is that LetsEncrypt requires users to renew their site certificates every three months, which can be a headache if users handle renewals manually. Programs like [certbot-auto](https://certbot.eff.org/docs/install.html) can automate the certificate renewal process, but the implementations for wildcard domains typically require DNS authentication and API access. Not every DNS provider (including Namecheap) provide an API that supports automating [ACME challenges](https://ietf-wg-acme.github.io/acme/draft-ietf-acme-acme.html) or may require users to pay an additional fee for access.
+
+**Luckily, it is possible for users to run their own DNS authentication server using [acme-dns](https://github.com/joohoi/acme-dns), which completely bypasses DNS provider limitations.**
+
+### Overview
+
+We will be running a small DNS server called acme-dns to respond to challenges issued by LetsEncrypt's certbot. You can run acme-dns on any computer, but typically it will run on the same host server as your website. Certbot will issue an ACME DNS challenge to your DNS provider, which will then forward the request via some redirection to your acme-dns server.
+
+### Assumptions
+
+You have a running web server that is properly configured to handle your site certificates. You are probably using Namecheap as a DNS host because you are deep enough in Google's search index to find my site.
+
+### Prerequisites
+
+I am using Ubuntu 16.04 for this tutorial, but it should not matter which distro you are using as long as you know how to modify the firewall and install the appropriate software from your package manager.
+
+1. Install a recent version of Certbot (via the PPA or EPEL)
+2. Install a recent version of golang-go (PPA is best option)
+3. Install acme-dns: `go get github.com/joohoi/acme-dns/…`
+4. Move the binary somewhere sensible since we will be using a systemd service: `sudo cp ~/go/bin/acme-dns /usr/local/bin/acme-dns`
+5. Make the necessary directories: `sudo mkdir /etc/acme-dns/ /var/lib/acme-dns`
+6. Make sure you've removed any existing _acme-challenge DNS records from your DNS host records
+
+### acme-dns configuration
+
+1. Create the following file, substituting your site's domain name for <yoursite\> and your server's IP address (yes the naming scheme is dumb, but leave "acme.", "ns1.acme.", etc):
+
+        #/etc/acme-dns/config.cfg
+        [general]
+        # DNS interface
+        listen = ":53"
+        protocol = "udp"
+        # domain name to serve the requests off of
+        domain = "acme.<yoursite>.com"
+        # zone name server
+        nsname = "ns1.acme.<yoursite>.com"
+        # admin email address, where @ is substituted with .
+        nsadmin = "admin.<yoursite>.com"
+        # predefined records served in addition to the TXT
+        records = [
+            "acme.<yoursite>.com. A 176.223.132.72",
+            "ns1.acme.<yoursite>.com. A 176.223.132.72",
+            "acme.<yoursite>.com. NS ns1.acme.<yoursite>.com.",
+        ]
+        debug = false
+
+        [database]
+        engine = "sqlite3"
+        connection = "/var/lib/acme-dns/acme-dns.db"
+
+        [api]
+        api_domain = ""
+        ip = "127.0.0.1"
+        disable_registration = false
+        autocert_port = "80"
+        port = "8081"
+        tls = "none"
+        corsorigins = [
+            "*"
+        ]
+        use_header = false
+        header_name = "X-Forwarded-For"
+
+        [logconfig]
+        loglevel = "debug"
+        logtype = "stdout"
+        logformat = "text"
+
+    A short explanation: you are configuring acme-dns to listen to DNS requests (from certbot via Namecheap) globally on the standard DNS port 53 and configuring the HTTP port for certbot to talk to acme-dns on port 8081 (since you are probably running something way cooler on port 8080).
+
+2. Since certbot has to traverse Namecheap to perform the challenge, we will need to open port 53 in the firewall (traffic on port 8081 is handled on the localhost, so we don't need to open that port): `sudo ufw allow 53/udp && sudo ufw reload`
+
+    **Update 4-10-2021:** Dynamic DNS users, please see [this comment](https://gist.github.com/Nimrodda/af1c35264799fed663088c01b71c9e21#gistcomment-3358700).
+
+3. Let's start the acme-dns program automatically on startup. Create:
+
+        # /etc/systemd/system/acme-dns.service
+        [Unit]
+        Description=Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely
+        After=network.target
+
+        [Service]
+        ExecStart=/usr/local/bin/acme-dns
+        Restart=on-failure
+
+        [Install]
+        WantedBy=multi-user.target
+
+    (Ubuntu 17.04+): you can security-harden the above script on distros running newer kernels by executing as a non-privileged user in conjunction with the `AmbientCapabilities=CAP_NET_BIND_SERVICE` line. However, older kernels will cause systemd to choke on that line during service startup. If you choose to execute as a non-root user make sure to chown the `/etc/acme-dns/` and `/var/lib/acme-dns` directories!
+
+4. Enable the service to run on startup and run it now: `sudo systemctl daemon-reload && sudo systemctl enable --now acme-dns.service`
+
+Great, now you've got a DNS authentication server that can respond to ACME challenges!
+
+### Initial Namecheap configuration
+
+You will need to add two DNS records:
+
+1. an NS record for acme.<yoursite\>.com pointing to ns1.acme.\<yoursite\>.com
+2. a record for ns1.acme.<yoursite\>.com pointing to the public IP address of your host
+
+Example: ![Example Namecheap DNS records](../assets/images/2019/02/example-namecheap-dns-records.png)
+
+### Configuring the Certbot auth hook
+
+Now you just need to get certbot and acme-dns to work together!
+
+1. Install python2 requests: `sudo apt-get install python-requests`
+2. Acquire the acme-dns certbot hook file: `sudo wget -O /etc/letsencrypt/acme-dns-auth.py https://raw.githubusercontent.com/joohoi/acme-dns-certbot-joohoi/master/acme-dns-auth.py`
+3. Configure the program you just downloaded: `sudo nano /etc/letsencrypt/acme-dns-auth.py` and change `ACMEDNS_URL = "http://localhost:8081"`
+
+### Run Certbot
+
+You will need to run certbot manually one time in order to be able to run `certbot renew` in the future to handle the certificate renewals manually. If you've followed the rest of this tutorial, go ahead and run certbot to acquire your certs:
+
+`sudo certbot certonly -d "*.<yoursite>.com" -d "<youresite>.com" --agree-tos --manual-public-ip-logging-ok --server https://acme-v02.api.letsencrypt.org/directory --preferred-challenges dns --manual --manual-auth-hook /etc/letsencrypt/acme-dns-auth.py --debug-challenges`
+
+When you run the command certbot will prompt you to add one more DNS CNAME record to your DNS host.
+
+Example: `_acme-challenge.<yoursite>.com CNAME ch30791e-33f4-1af1-7db3-1ae95ecdde28.acme.<yoursite>.com.`
+
+Create a new CNAME record named `_acme-challenge` and give it a value of `ch30791e-33f4-1af1-7db3-1ae95ecdde28.acme.<yoursite>.com.`
+
+Wait a few minutes and hit <Enter\> to complete the ACME challenge and receive your certificates!
+
+### Automation
+
+The step I'm sure you've been waiting for.
+
+1. Create the certbot-renew.service (if you are using Apache in lieu of nginx, substitute "nginx" with "httpd"):
+
+        #/etc/systemd/system/certbot-renew.service
+        [Unit]
+        Description=Certbot Renewal
+
+        [Service]
+        ExecStart=/usr/bin/certbot renew --post-hook "systemctl restart nginx"
+
+2. Create the associated timer file to run the renewal weekly:
+
+        #/etc/systemd/system/certbot-renew.timer
+        [Unit]
+        Description=Timer for Certbot Renewal
+
+        [Timer]
+        OnBootSec=300
+        OnUnitActiveSec=1w
+
+        [Install]
+        WantedBy=multi-user.target
+
+3. Enable the timer: `sudo systemctl enable certbot-renew.timer`
+
+### What the hell is going on here?
+
+A wild goose chase:
+
+1. LetsEncrypt first asks your <yoursite\>.com domain for the TXT record at _acme-challenge.example.com to complete the challenge
+2. The Namecheap DNS server responds with a CNAME record that points to ch30791e-33f4-1af1-7db3-1ae95ecdde28.acme.*yoursite*.com, so LetsEncrypt goes there instead
+3. The authoritative DNS server for \*.acme.*yoursite*.com is ns1.acme.*yoursite*.com, which points at your server IP (running acme-dns)
+4. LetsEncrypt can finally ask ns1.acme.example.com what is the TXT record for ch30791e-33f4-1af1-7db3-1ae95ecdde28.acme.*yoursite*.com and acme-dns will answer that question
+
+### Additional Considerations
+
+On a critical server it may be a good idea to start and stop acme-dns (and open and close port 53) alongside certbot execution. This can be handled fairly trivially with systemd `Requires=`, but I'll leave that up to you!
+
+### Conclusions
+
+Congratulations! You have successfully enabled automatic LetsEncrypt site certificate renewal on a finicky DNS host provider!

blog.bryanroessler.com/_posts/2019-05-21-headless-x2go-server-for-remote-gui-applications.md

@@ -0,0 +1,117 @@
+---
+layout: post
+title: Configuring a lightweight headless X2Go server for managing remote GUI applications
+subtitle:
+#bigimg: /img/path.jpg
+tags: [x2go, X11, getty, systemd, autologin, openbox, jriver]
+---
+
+While it is certainly preferable to manage server applications via the terminal, sometimes it is not feasible for programs that rely on a GUI for their function. In this example I am using [JRiver Media Center](https://yabb.jriver.com/interact/index.php) as a media server for my audio and video files located on a remote VPS. Streaming to my devices from the VPS prevents me from saturating my home upload bandwidth or risk going over my ISP data caps. However, JRiver Media Center requires an existing X server to run its media server, and resources on the VPS I am using are tight (1GB RAM and 1 vCPU).
+
+Luckily it is not necessary to run a full DE on a headless server in order to satisfy such program's requirements.
+
+In this tutorial we will be setting up a headless X server that utilizes autologin, [Openbox WM](http://openbox.org/wiki/Main_Page), and X2Go to provide a lightweight GUI-based remote administration portal that also satisfies the requirements of JRiver Media Center's media server.
+
+### X2Go versus VNC
+
+TigerVNC can create its own X server using its virtual framebuffer, so it is the most commonly recommended solution for starting a remotely accessible X session. However, I prefer to use X2Go as my go-to remote desktop software on Linux due to its easy setup, performance, strong security (since it utilizes the existing ssh stack), and multi-platform client availability. It is also much easier for end users to configure because it does not rely on them to set up SSH tunnels to securely access the remote desktop. Additionally, X2Go utilizes the [NX protocol](https://en.wikipedia.org/wiki/NX_technology) which offers superior performance, latency, and quality than VNC. Another interesting option on the horizon is [Apache's Guacamole](https://guacamole.apache.org/), which uses HTML5 to provide remote desktop capabilities in the client's browser, but in this article I will be sticking to X2Go.
+
+### Display Manager (or not)
+
+In most situations, a display manager alleviates a lot of headaches regarding user login, starting X, and handling process management. However, since we are trying to minimize resource usage on the server for the purposes of this tutorial, we will be avoiding the additional overhead of a display manager and instead use systemd to autologin and then launch the X session.
+
+### Window Manager
+
+Using a window manager will simplify launching and maintaining your graphical programs. There are many to choose from, in this tutorial I will be using openbox due to its wide adoption and low memory footprint.
+
+### Prerequisites
+
+1. Install x2go, a window manager, and a terminal emulator: `sudo apt-get install x2goserver python openbox xterm`
+
+2. Configure your SSH server and firewall for remote access. For testing, password-based authentication is OK, but eventually you will want to switch to using SSH keys for security and ease-of-use.
+
+### Enabling autologin
+
+We will be using getty to handle autologin for our user. In order to do this, we must override the default getty settings which normally prompts for a username and password upon login.
+
+1. `sudo systemctl edit getty@tty1`
+
+This will open your default system editor to create an override service file for the systemd getty@tty1.service.
+
+2. Enter the following into the drop-in override file you just opened/created and save it (replacing username with your actual username):
+
+```(text)
+[Service]
+Type=simple
+ExecStart=
+ExecStart=-/sbin/agetty --autologin username --noclear %I $TERM
+```
+
+3. Reload, restart, and enable the service file to load on boot: `sudo systemctl daemon-reload && sudo systemctl restart getty@tty1 && sudo systemctl enable getty@tty1`
+
+Your system will now autologin the user you specified when you reboot!
+
+### Starting the graphical X server automatically
+
+In order to run a graphical program or window manager, you will first need to initiate an X server. We can start one automatically using a shell profile file that is sourced during user login. The location of this file (e.g. `/etc/profile.d/`, `~/.profile`, `~/.bash_profile`, `~/.zprofile` (zsh), etc.) depends on your Linux distribution and shell settings. Here I am assuming that you are using bash shell (you can confirm this via the `echo $SHELL` command), thus we will place the relevant commands in `~/.bash_profile`.
+
+1. Add the following to the end of your `~/.bash_profile`:
+
+```(bash)
+# Start X11 automatically
+if [[ -z "$DISPLAY" ]] && [[ $(tty) = /dev/tty1 ]]; then
+        . startx
+        logout
+fi
+```
+
+Now that the X server is set to run on login, it needs to be configured to start your window manager, in this case Openbox.
+
+2. Add the following line to `~/.xinitrc` and save the file:
+
+```(bash)
+exec openbox-session
+```
+
+Now your server is configured to automatically login, start an X server, and run Openbox!
+
+### Using systemd to automatically start your GUI programs
+
+It's certainly possible to use Openbox to autostart your server's GUI programs by adding its start command to `~/.config/openbox/autostart`; however, on a server it is preferable to use systemd to reliably manage programs as services (e.g. Openbox will not automatically restart crashed programs).
+
+Here are the necessary steps to create and activate a systemd service file to start and stop JRiver Media Center.
+
+1. Create the file `/etc/systemd/system/jriver.service` and add the following (replacing username with your username):
+
+```(text)
+[Unit]
+Description=JRiver Media Center 25
+After=graphical.target
+#
+[Service]
+Type=simple
+Environment=DISPLAY=:0
+User=username
+ExecStart=/usr/bin/mediacenter25 /MediaServer
+Restart=always
+RestartSec=10
+KillSignal=SIGHUP
+TimeoutStopSec=45
+#
+[Install]
+WantedBy=graphical.target
+```
+
+The key here is the `After=graphical.target` condition that will launch the program only after X has started. There are plenty of additional systemd options that can be used for sandboxing or to improve process management using PID files, but that is outside the scope of this article.
+
+2. Reload, restart, and enable the service file to load on boot: `sudo systemctl daemon-reload && sudo systemctl enable --now jriver.service`
+
+### Testing the remote desktop using X2Go
+
+At this point, go ahead and reboot the server in order to test it, using X2Go to connect using your SSH credentials. In the session preferences, ensure that the session type is set to "Connect to local desktop". If the session window appears to be an empty black box, try right-clicking to bring up the Openbox context menu.
+
+![X2Go configuration settings](../assets/images/2019/05/x2go-configuration-settings.png)
+
+### Conclusions
+
+In this tutorial you have learned how to autologin a user, start the X display server, launch a lightweight window manager, enable a GUI service using systemd, and connect to the remote desktop you created using X2Go. Very cool!

blog.bryanroessler.com/_posts/2019-06-12-jriver-client-client-model-with-syncthing.md

@@ -0,0 +1,112 @@
+---
+layout: "post"
+title: "JRiver Media Center: the client-client model"
+subtitle:
+#bigimg: /img/path.jpg
+tags: [jriver, syncthing]
+---
+
+### Introduction
+
+My goals for using JRiver Media Center (JRMC) successfully are as follows:
+
+1. Enjoy my music when I want, where I want
+    - Make it easy to access
+    - Keep my media library organized
+    - Make it easy to add and remove media
+    - Keep my media library consistent across many devices
+2. Minimize the impact on my home's bandwidth and ISP data caps
+3. Automatically create redundant backups of my media
+4. Make it stable
+5. Make it automated
+
+In the course of achieving these goals, my JRMC network has been in a state of flux for several years. However, I have eventually settled into a configuration that I have found works very well: pairing continuous file synchronization with JRMC automatic read and write tagging to synchronize media libraries among two or more JRMC clients, which I have termed the **client-client model**.
+
+### Pairing JRMC with continuous file synchronization
+
+JRMC contains a powerful [Media Server](https://wiki.jriver.com/index.php/Media_Server) that enables clients to play and manage media in JRMC as if they were using a local copy of the library. It is certainly possible to use JRMC Media Server exclusively to manage and play your media from the server to your clients in the traditional server-client model.
+
+JRMC Media Server pros:
+
+1. Tag changes are synced seamlessly between all devices
+2. Client devices are easy to add/remove
+
+JRMC Media Server cons:
+
+1. Internet-connectivity, bandwidth and latency. Media must always be streamed from the server to the playback clients, which means that clients must have internet connectivity to access the library. I travel frequently so streaming is not always a feasible option. Also, file operations will not be as responsive as using a local library because the library will need to buffer media during playback and sync tag changes.
+2. Adding new music to the server must still be done through a third-party tool (e.g. sftp, rsync, etc.)
+
+Con #1 can be alleviated by maintaining a duplicate local copy of the media files on a client device and enabling the option to *Options>Media Network>Client Options>Play local file if one that matches Library Server file is found* on the client's copy of JRMC. However, this feature necessitates that the client and server file structures are identical, which is problematic for clients and servers running on different platforms (hopefully this limitation can be fixed at some point in the future by the JRMC developers).
+
+Luckily, both cons can be eliminated if we introduce a third-party tool to keep the media libraries continuously in sync, so that 1) newly added media is propagated between the server and clients and 2) directory structure and filenames are always identical. The answer here is [Syncthing](https://syncthing.net/), an open-source multi-platform tool for continuous file synchronization between many clients.
+
+### Syncthing
+
+Syncthing is easily the most important tool in my arsenal to keep all of my various devices working in harmony. I use it on my smartphone (well, [syncthing-fork](https://f-droid.org/en/packages/com.github.catfriend1.syncthingandroid) for better battery life) to sync podcasts, photos, and documents to my laptop and desktop. I use it on my high-performance workstations to create rolling off-site backups. I use it on my servers to share configuration settings and dotfiles. Every second of every day I have bytes floating through my Syncthing cloud and it has yet to fail me.
+
+Syncthing configuration is relatively straight-forward, thus I will not go into much depth here other than to highlight a few important settings for improving the reliability. If you have a client device that will not be adding or tagging media (in essence, a read-only client), then make sure to set the Syncthing share to "receive only" instead of the default "send and receive," which will save a few CPU cycles and prevent read-only clients from accidentally altering your media library. Additionally, make sure that the filesystem watcher is enabled so that any changes to your media files are propagated as quickly as possible to other devices.
+
+![Syncthing shares](../assets/images/2019/05/syncthing-shares.png)
+
+At this point you will have a fully in-sync media library residing on one or more computers. The real magic comes next when we start using JRMC to apply changes to file tags, which will also be propagated to other devices since tag changes will alter the file checksums. Since Syncthing is a block-based synchronization tool, any changes to a file's tags will not necessitate the entire file to be transferred to other clients, only a small block of data (typically a few KB), which makes it fast and bandwidth-friendly.
+
+![Syncthing music folder configuration](../assets/images/2019/06/syncthing-music-folder-configuration.png)
+
+### Client-client model versus the traditional server-client model
+
+Although our media files are now in sync, and we have configured JRMC to use local file playback to save bandwidth and improve latency, the server-client model using JRMC Media Server still requires internet connectivity to function, which limits its reliability. However, we can eschew the JRMC Media Server altogether and instead utilize Syncthing to keep the separate libraries on our clients nearly identical via file tags, with one caveat:
+
+**When using the client-client model, traditional playlists will not be automatically synced among clients** since they are stored in the JRMC library and are only exported as files when manually triggered. Later on I will describe a method later on in this guide that can replace playlist functionality using JRMC smartlists and file tags.
+
+**Rant:** *On several occasions, I have asked the JRMC developers to consider adding an automatic playlist export core command so that Syncthing could also sync the playlist files, but they have chosen not to do so thus far. You can get close by using [the RESTful MCWS interface](https://wiki.jriver.com/index.php/Web_Service_Interface) and appropriate [JRMC core command](https://wiki.jriver.com/index.php/Media_Center_Core_Commands): `curl -s -o /dev/null -u username:password http://localhost:52199/MCWS/v1/Control/MCC?Command=20004,1`, however MC will still prompt you for the export directory and playlist format so it cannot be automated.*
+
+The benefits of the client-client model over the server-client model include:
+
+- Automatic redundancy of the media library
+- Each client has access to the media library even when offline
+- Each client can maintain its own set of views, playlists, and smartlists
+  - Useful if you want to give read-only access to a client and allow it to store and display its own set of ratings from a custom tag
+- Low bandwidth and low latency for playback
+- Cross-platform since file structure does not have to be identical
+
+All that must be done to enable this functionality is to set up Auto-Import on each client to point at your shared (via Syncthing) media folder!
+
+### Consistent tagging is the key to the client-client model
+
+The real magic here is to store as much information as possible in the file tags so that they are synced via Syncthing between JRMC clients. This can include basic information like ratings, artwork, audio analysis data (R128 normalization) or more advanced information like user-defined fields that can be used to keep smartlists in sync (see [Advanced tagging](#advanced-tagging) below for more information).
+
+#### Sending metadata
+
+To propagate changes from a client to other clients, we will need to enable *Edit>Edit File Tags When File Info Changes* on any JRMC client that we want to have read-write access to the file metadata. If you leave this option unchecked on a client then that client will maintain its own set of metadata in the JRMC database without propagating changes. If you want to edit the actual file tags without affecting other clients (e.g. you are moving files on the client to a handheld device), then go ahead and enable the option but set your Syncthing client to Receive Only so that it maintains its own local database state. I also recommend enabling automatic file tagging during file analysis upon Auto-Import *Options>Library & Folders>Configure auto-import>Tasks>Write file tags when analyzing audio...* so that analysis only needs to be performed once on the client that performs the initial file import.
+
+##### Receiving metadata
+
+In order to receive metadata updates from other clients, you'll want to use JRMC Auto-Import to watch the Syncthing music directory for changes and enable *Options>Library & Folders>Configure auto-import>Tasks>Update for external changes*.
+
+![Auto-import settings](../assets/images/2019/06/auto-import-settings.png)
+
+### Advanced tagging
+
+Below I will describe two examples of expanding the functionality of the client-client model using file tags.
+
+#### Tracking newly added media
+
+Sometimes it is useful to keep track of which client has added a particular file to the Syncthing network. You can do this by creating a custom user-defined string field in JRMC (*Options>Library & Folders>Manage Library Fields*) named *Imported From* and check the box to *Save in file tags (when possible)*. Then configure each client to apply their specific client name to the field upon auto-import: In *Options>Library & Folders>Configure auto-import* select your auto-import directory that you are sharing with Syncthing, click *Edit...* and under *Apply these tags (optional)>Add>Custom* select the field you just created and enter the client name as the value. For instance I have named my clients *HTPC*, *Laptop*, *VPS*, and *Work*. In this manner you can track where your files were originally imported from.
+
+![Imported From custom field](../assets/images/2019/06/imported-from-custom-field.png)
+
+It can also be useful to use a smartlist to track newly imported media to make sure that you actually listen to it before it falls to the proverbial wayside. In this case, follow the strategy above to create a check field called *Newly Imported* that is tagged as "1" upon auto-import. Then just create a smartlist on each client that lists files with a *Newly Imported* value of 1 (optionally sorted by \[Date Imported\]). After you watch or listen to the file, simply clear the *Newly Imported* field to remove it from the smartlist on every client!
+
+##### Smartlists as pseudo-playlists
+
+As I outlined above it is possible use file tags in conjunction with smartlists to keep advanced file information and file lists in sync between clients. In this manner it is also possible to partially restore the ability to sync playlists between clients. In order to do this, create a new User Field named *User Playlists* with a data type of *List*. Use this field to create a semi-colon delimited list of pseudo-playlists. On each client, create a smartlist that only displays files with the matching string in the *User Playlists* field. When you want to add a file to the pseudo-playlist, simply add that playlist string to the *User Playlists* field. One drawback of this method is that it is not easy to manually reorder the smartlist for specific track ordering, but it can be done if necessary using additional user fields and/or smartlist rules to maintain the track order.
+
+![User Playlists Field](../assets/images/2019/06/user-playlists-field.png)
+
+![Top Hits Today Playlist](../assets/images/2019/06/top-hits-today-playlist.png)
+
+This is just the tip of the iceberg when it comes to using file tags to share library information between clients in the client-client model.
+
+### Conclusions
+
+In this guide you have been shown the benefits of using a client-client JRMC network model over the traditional server-client network model used by JRMC Media Server. The client-client model allow individual clients to maintain their own instances of the file library and JRMC database, while propagating changes to other clients using file-based synchronization.

blog.bryanroessler.com/_posts/2020-01-23-run-with-podman.md

@@ -0,0 +1,357 @@
+---
+layout: post
+title: Developing in containers using podman and container management scripts
+subtitle: Now with systemd!
+#bigimg: /img/path.jpg
+tags: [atom, podman, containers, ide, systemd, run-with-podman]
+---
+
+## Note
+
+**The scripts provided in this tutorial have been superseded by the simpler [podmanRun]({% post_url 2020-05-15-podmanrun-a-simple-podman-wrapper %}) wrapper.**
+
+## Overview
+
+In this tutorial we will be using Atom's [build package](https://atom.io/packages/build) (although you are free to use your own IDE) and a container management script to run files/commands on default system images using podman. We will go one step further by enabling systemd support in our build environment. We will also provide the option of masking the program's output from the host using unnamed volumes.
+
+## Introduction
+
+It is important to remember that a development environment can be just as important as the code itself. Over time, our development environment morphs into a unique beast that are specific to each user. Therefore, it is imperative to test your programs in several default environments prior to distribution.
+
+In the past, this was performed on virtual machines (VMs) that contained a default installation of the distribution that you were targeting. Thanks to their snapshotting abilities it was fairly trivial to restore distributions to their default state for software testing. However, this method had its drawbacks:
+
+* The default state was never the *current* default state for long. VMs had to be continually upgraded via their package managers to stay up-to-date with the development environment. They also needed to be modified in some cases (e.g. to enable sshd and allow authentication-less sudo) so deploying newer image versions required manual intervention
+* Retroactive changes to existing VMs is difficult
+* VMs are difficult to automate, requiring third-party tools (e.g. kickstart files, Ansible, etc.) to manage them
+* Each VM gets its own IP address, which makes it difficult to automate ssh-based program building/script running
+* VMs are computationally heavy. Their footprint is an entire deduplication of the host OS and its virtualization stack, in both memory and disk space. Taking and restoring snapshots is slow.
+* There is a meaningful amount of performance loss between the hypervisor and disk i/o because it is handled using network protocols. For example, an Atom VM build command would normally look something like this:
+
+```bash
+cat {FILE_ACTIVE} | ssh fedora-build-machine.lan "cat > /tmp/{FILE_ACTIVE_NAME} ; mkdir -p {FILE_ACTIVE_NAME_BASE}; cd {FILE_ACTIVE_NAME_BASE}; chmod 755 /tmp/{FILE_ACTIVE_NAME} ; /tmp/{FILE_ACTIVE_NAME}"
+```
+
+In short, it takes a solid understanding of many different tools and decent scripting skills for a subpar experience using VMs as development environments.
+
+### Enter containers
+
+Containers alleviate all of the problems associated with using VMs to execute code.
+
+They:
+
+* Use standardized images of your target distributions and make it possible to execute commands directly on them
+* Allow you to create your own custom base images using Dockerfiles, which are built on top of other rolling images that are automatically maintained
+* Support several different networking options, such as automatically using the host network or operating via its own whitelisted service
+* Perform great because the code is running on the same kernel as the OS
+* Can be created and destroyed nearly instantaneously which makes them much better for executing frequent build commands (I'm a big F5'er)
+
+### Podman and Toolbox
+
+Podman is a container manager by Red Hat that is available on Fedora and CentOS and integral to Silverblue and CoreOS. Red Hat has also shipped some fun stuff built on top of Podman such as [Toolbox](https://fedoramagazine.org/a-quick-introduction-to-toolbox-on-fedora/) that combine system overlays and containers to provide seamless build environments for past and current CentOS and Fedora releases (theoretically you should be able to provide your own custom image although the documentation is currently scant). Toolbox will get you 90% of the way there to automated builds as long as you:
+
+* only target Red Hat-based distributions
+* don't develop or test systemd scripts or need to utilize existing systemd services (**systemd does not work in Toolbox**)
+* are comfortable with having your entire $HOME exposed to your build environment
+* don't need to nest toolboxes
+
+Toolbox may make sense if you run separate instances of your IDE from *inside* the toolbox containers, but then you are just back to creating custom build environments within each container, only now separated from the host OS. Unfortunately, Toolbox does not support nesting containers so testing your code on default images from within a toolbox is impossible as of this moment. Additionally, if your scripts change environmental variables, they may be difficult to test as the toolbox is mutable.
+
+### Prerequisites
+
+1. You have a script or command to execute on build. Let's start with something easy like:
+
+```bash
+#!/usr/bin/env bash
+# ./hello-pwd-ls.sh
+echo "Hello!" | tee output/hello.txt
+pwd
+ls -al
+exit $?
+```
+
+2. You have [Atom](https://atom.io/) and the [build](https://atom.io/packages/build) package installed (the podman commands I will highlight in this post will work equally as well using whichever IDE you choose to use in conjunction with its external build commands.)
+3. You are somewhat familiar with .atom-build.yml (or can copypasta)
+4. You have podman installed
+
+### Configuration
+
+#### run-with-podman.sh
+
+I created the following script to handle container execution depending on a few arguments. You can download it and place it in your path here:
+
+Download [run-with-podman.sh](https://git.bryanroessler.com/bryan/run-with-podman/src/master/run-with-podman.sh) and install to `$HOME/.local/bin`:
+
+```bash
+wget -q -O "${HOME}/.local/bin/run-with-podman" "https://git.bryanroessler.com/bryan/run-with-podman/src/master/run-with-podman.sh"
+```
+
+If you prefer to copy-paste:
+
+```bash
+#!/usr/bin/env bash
+
+# README; print this help message
+print_help () {
+
+    cat <<-'EOF'
+Usage: run-with-podman.sh --file FILE [--file-path PATH] [--mode [0,1,2]]
+                              [--mask-dir PATH] [--image IMAGE_NAME] [--force-systemd]
+                              [--help] [--] $OPTIONS
+
+    --file,-f FILE
+        The local script to execute in the container (typically sent from your IDE)
+
+    --file-path PATH
+        Path that the script operates on (Default: the --file directory)
+
+    --mode,-m 0,1,2
+        0. Nonpersistent container (always recreate) (Default)
+        1. Persistent container
+        2. Recreate persistent container
+
+    --mask-dir PATH
+        Hide this directory from the host OS, store contents in the container only (Default: unset)
+        (Useful for capturing output in the container only for easy reset)
+
+    --image,-i IMAGE_NAME
+        The name of the image to execute the script (Default: fedora:latest)
+
+    --force-systemd
+        Force container to init with systemd
+
+    --help,-h
+        Print this help message and exit
+
+    -- [additional arguments to pass to --file FILE]
+        Parsed as "quoted string"
+EOF
+}
+
+# DEFAULTS
+MODE="0"
+IMAGE="fedora:latest"
+SYSTEMD="on" # "on" is the podman default; "always" forces systemd init
+
+# Parse input
+function parse_input () {
+    if options=$(getopt -o fmih -l file:,file-path:,mode:,mask-dir:,image:,force-systemd,help -- "$@"); then
+
+        eval set -- "$options"
+        while true; do
+            case "$1" in
+            --file| -f)
+                shift
+                FILE_ACTIVE="$1"
+                ;;
+            --file-path)
+                shift
+                FILE_ACTIVE_PATH="$1"
+                ;;
+            --mode| -m)
+                shift
+                MODE="$1"
+                ;;
+            --mask-dir)
+                shift
+                MASK_DIR="$1"
+                ;;
+            --image| -i)
+                shift
+                IMAGE="$1"
+                ;;
+            --force-systemd)
+                SYSTEMD="always" # force systemd init
+                ;;
+            --help |-h)
+                print_help
+                exit $?
+                ;;
+            --)
+                shift
+                break
+                ;;
+            esac
+            shift
+        done
+    else
+        echo "Incorrect options provided"
+        exit 1
+    fi
+
+    [[ -z $FILE_ACTIVE ]] && echo "You must provide a --file" && exit 1
+
+    # If --file-path not set, extract FILE_ACTIVE_PATH from FILE_ACTIVE
+    [[ -z $FILE_ACTIVE_PATH ]] && FILE_ACTIVE_PATH=${FILE_ACTIVE%/*}
+    ! [[ -d "$FILE_ACTIVE_PATH" ]] &&
+
+    # Pass any remaining positional arguments as script options
+    OPTIONS=${*:$OPTIND}
+}
+
+# Get input
+parse_input "${@}"
+
+# Sanitize filename for unique container name
+CLEAN="${FILE_ACTIVE//_/}" && CLEAN="${CLEAN//[^a-zA-Z0-9]/}" && CLEAN="${CLEAN,,}"
+
+# Allow container access to the pwd
+chcon -t container_file_t -R "${FILE_ACTIVE_PATH}"
+
+# Nonpersistent container (always recreate)
+if [[ $MODE == "0" ]]; then
+    if podman container exists "atom-${CLEAN}-nonpersistent"; then
+        podman rm -v -f "atom-${CLEAN}-nonpersistent"
+    fi
+    echo "Building in nonpersistent container: atom-${CLEAN}-nonpersistent"
+    if [[ -n $MASK_DIR ]]; then
+        podman run \
+            -it \
+            --systemd="${SYSTEMD}" \
+            --name "atom-${CLEAN}-nonpersistent" \
+            -v "${FILE_ACTIVE_PATH}:${FILE_ACTIVE_PATH}" \
+            -v "${FILE_ACTIVE_PATH}/${MASK_DIR}" \
+            -w "${FILE_ACTIVE_PATH}" \
+            "${IMAGE}" \
+            /bin/bash -c "chmod 755 ${FILE_ACTIVE} && ${FILE_ACTIVE} ${OPTIONS}"
+    else
+        podman run \
+            -it \
+            --systemd="${SYSTEMD}" \
+            --name "atom-${CLEAN}-nonpersistent" \
+            -v "${FILE_ACTIVE_PATH}:${FILE_ACTIVE_PATH}" \
+            -w "${FILE_ACTIVE_PATH}" \
+            "${IMAGE}" \
+            /bin/bash -c "chmod 755 ${FILE_ACTIVE} && ${FILE_ACTIVE} ${OPTIONS}"
+    fi
+# Persistent container
+elif [[ $MODE == "1" ]]; then
+    echo "Reusing container: atom-${CLEAN}-persistent"
+    if podman container exists "atom-${CLEAN}-persistent"; then
+        echo "Using existing container!"
+        podman exec "atom-${CLEAN}-persistent" \
+        /bin/bash -c "chmod 755 {FILE_ACTIVE} && {FILE_ACTIVE}"
+    else
+        if [[ -n $MASK_DIR ]]; then
+            podman run \
+            -it \
+            --systemd="${SYSTEMD}" \
+            --name "atom-${CLEAN}-persistent" \
+            -v "${FILE_ACTIVE_PATH}:${FILE_ACTIVE_PATH}" \
+            -v "${FILE_ACTIVE_PATH}/${MASK_DIR}" \
+            -w "${FILE_ACTIVE_PATH}" \
+            "${IMAGE}" \
+            /bin/bash -c "chmod 755 ${FILE_ACTIVE} && ${FILE_ACTIVE} ${OPTIONS}"
+        else
+            podman run \
+            -it \
+            --systemd="${SYSTEMD}" \
+            --name "atom-${CLEAN}-persistent" \
+            -v "${FILE_ACTIVE_PATH}:${FILE_ACTIVE_PATH}" \
+            -w "${FILE_ACTIVE_PATH}" \
+            "${IMAGE}" \
+            /bin/bash -c "chmod 755 ${FILE_ACTIVE} && ${FILE_ACTIVE} ${OPTIONS}"
+        fi
+    fi
+# Recreate persistent container
+elif [[ $MODE == "2" ]]; then
+    echo "Building in container: atom-${CLEAN}-persistent"
+    if podman container exists "atom-${CLEAN}-persistent"; then
+        echo "Container exists! Resetting container."
+        podman rm -v -f "atom-${CLEAN}-persistent"
+    fi
+    if [[ -n $MASK_DIR ]]; then
+        podman run \
+        -it \
+        --systemd="${SYSTEMD}" \
+        --name "atom-${CLEAN}-persistent" \
+        -v "${FILE_ACTIVE_PATH}:${FILE_ACTIVE_PATH}" \
+        -v "${FILE_ACTIVE_PATH}/${MASK_DIR}" \
+        -w "${FILE_ACTIVE_PATH}" \
+        "${IMAGE}" \
+        /bin/bash -c "chmod 755 ${FILE_ACTIVE} && ${FILE_ACTIVE} ${OPTIONS}"
+    else
+        podman run \
+        -it \
+        --systemd="${SYSTEMD}" \
+        --name "atom-${CLEAN}-persistent" \
+        -v "${FILE_ACTIVE_PATH}:${FILE_ACTIVE_PATH}" \
+        -w "${FILE_ACTIVE_PATH}" \
+        "${IMAGE}" \
+        /bin/bash -c "chmod 755 ${FILE_ACTIVE} && ${FILE_ACTIVE} ${OPTIONS}"
+    fi
+fi
+
+```
+
+There are several things to highlight in this script:
+
+1. The filename is first sanitized so that it can be used to generate a unique container name.
+2. Next, we edit SELinux permissions on our `pwd` to allow the container full access to our build directory. Editing SELinux permissions is always a balance between ease-of-use and security and I find setting the container_file_t flag is a nice balance. If your script doesn't do much file i/o it may be possible to run it by only altering permissions on `$FILE_ACTIVE`.
+3. According to the mode we either remove and recreate or create a new container
+4. We mount the `pwd` in the container
+5. If `OUTPUT=0`, we mask the output directory `-v "{FILE_ACTIVE_PATH}/${OUTPUT_DIR}"` by mounting an unnamed volume, so that output is only stored in the container and not on the host filesystem. You can repeat this as many times as necessary to exclude other subdirectories in your build directory.
+6. Enable `--systemd=always` if you plan on interacting with `systemctl` using your script. The default `on` state will only enable systemd when the command passed to the container is `/usr/sbin/init`. Since it is not possible to pass more than one command and we must pass our script, this should be set to `always`.
+7. Make sure to make the script executable in the container using `chmod 755`
+
+##### `--file` and `--file-path`
+
+The file or command that you want to run in the container. If missing, `--file-path` will be generated from the `pwd` of the `--file`.
+
+This can be a script running a list of commands (e.g. build script) or a single command to be executed.
+
+##### `--mode`
+
+0. Nonpersistent container (always recreate) (Default)
+1. Persistent container
+2. Recreate persistent container
+
+##### `--mask-dir`
+
+Optionally, one can mask output from the host system (so that it only resides in a container volume) using `--mask-dir`.  As demonstrated in the [prerequisites](#prerequisites), it is important to have your program output to the `--` specified in your `.atom-build.yml` (in this case 'output'). This provides you the ability to optionally mask the output directory with an unnamed volume so that no files are actually written to the host. This has two benefits:
+
+* If the script is configured to overwrite existing output, it may threaten a live system (like a website or any other running process that depends on the script output)
+* If the script is configured to not overwrite existing output, the script may not run correctly
+
+Output masking gives you the power to control these variables independently of one another by writing output to the container only.
+
+##### `--force-systemd`
+
+Typically, containers are used to run microservices where *n* containers is equal to *n* processes. While that is good design for microservices, it is still possible to use a process manager to create multi-service containers for purposes other than microservices (in this case a development environment).
+
+If you are going to release software that integrates with systemd, it is certainly worthwhile to test your services beforehand in a containerized environment. By using `podman` along with the `--systemd=always` option mentioned [above](#atom-container-build.sh), we can initialize an interactive systemd process *and* execute our script.
+
+##### `--image`
+
+The container image to be used to execute the command.
+
+#### .atom-build.yml
+
+In your project directory (next to your script), create the following `.atom-build.yml` file in order to call our script using the appropriate arguments whenever a build is triggered.
+
+```yaml
+cmd: 'run-with-podman.sh --file {FILE_ACTIVE} --file-path {FILE_ACTIVE_PATH} --mode 0 --mask-dir output --image fedora:latest --force-systemd'
+name: 'Nonpersistent F31 container w/ systemd'
+targets:
+  Persistent F31 container w/ systemd:
+    cmd: 'run-with-podman.sh --file {FILE_ACTIVE} --file-path {FILE_ACTIVE_PATH} --mode 1 --mask-dir output --image fedora:latest --force-systemd'
+  Reset and run persistent F31 container w/ systemd:
+    cmd: 'run-with-podman.sh --file {FILE_ACTIVE} --file-path {FILE_ACTIVE_PATH} --mode 2 --mask-dir output --image fedora:latest --force-systemd'
+  Nonpersistent F31 container w/ output & systemd:
+    cmd: 'run-with-podman.sh --file {FILE_ACTIVE} --file-path {FILE_ACTIVE_PATH} --mode 0 --image fedora:latest --force-systemd'
+  Persistent F31 container w/ output & systemd:
+    cmd: 'run-with-podman.sh --file {FILE_ACTIVE} --file-path {FILE_ACTIVE_PATH} --mode 1 --image fedora:latest --force-systemd'
+  Reset and run persistent F31 container w/ output & systemd:
+    cmd: 'run-with-podman.sh --file {FILE_ACTIVE} --file-path {FILE_ACTIVE_PATH} --mode 2 --image fedora:latest --force-systemd'
+```
+
+This `.atom-build.yml` can be as complicated as you need it to be, in fact you can perform all of the same shell functions as `atom-container-build.sh` in a `cmd` argument; however, I find it cleaner and easier to break the shell script out of YAML and pass simple arguments instead.
+
+There are plenty of other options available in the build package to set the environment of your script, or you can pass them as arguments following `--` in your `cmd`.
+
+You can also run build using any external build file, you are not just limited to executing the `{FILE_ACTIVE}`.
+
+Save your files and run the appropriate build command on your script! Now you're developing in containers!
+
+### Conclusions
+
+Developing in containers can be streamlined using tools like `podman` and container management scripts like I provided [earlier](#run-with-podman.sh).

blog.bryanroessler.com/_posts/2020-02-26-flake-it-till-you-make-it.md

@@ -0,0 +1,18 @@
+---
+layout: post
+title: Flake it till you make it
+subtitle: Excerpt from Soulshaping by Jeff Brown
+cover-img: /assets/img/path.jpg
+thumbnail-img: /assets/img/thumb.png
+share-img: /assets/img/path.jpg
+tags: [books, test]
+author: Sharon Smith and Barry Simpson
+---
+
+Under what circumstances should we step off a path? When is it essential that we finish what we start? If I bought a bag of peanuts and had an allergic reaction, no one would fault me if I threw it out. If I ended a relationship with a woman who hit me, no one would say that I had a commitment problem. But if I walk away from a seemingly secure route because my soul has other ideas, I am a flake?
+
+The truth is that no one else can definitively know the path we are here to walk. It’s tempting to listen—many of us long for the omnipotent other—but unless they are genuine psychic intuitives, they can’t know. All others can know is their own truth, and if they’ve actually done the work to excavate it, they will have the good sense to know that they cannot genuinely know anyone else’s. Only soul knows the path it is here to walk. Since you are the only one living in your temple, only you can know its scriptures and interpretive structure.
+
+At the heart of the struggle are two very different ideas of success—survival-driven and soul-driven. For survivalists, success is security, pragmatism, power over others. Success is the absence of material suffering, the nourishing of the soul be damned. It is an odd and ironic thing that most of the material power in our world often resides in the hands of younger souls. Still working in the egoic and material realms, they love the sensations of power and focus most of their energy on accumulation. Older souls tend not to be as materially driven. They have already played the worldly game in previous lives and they search for more subtle shades of meaning in this one—authentication rather than accumulation. They are often ignored by the culture at large, although they really are the truest warriors.
+
+A soulful notion of success rests on the actualization of our innate image. Success is simply the completion of a soul step, however unsightly it may be. We have finished what we started when the lesson is learned. What a fear-based culture calls a wonderful opportunity may be fruitless and misguided for the soul. Staying in a passionless relationship may satisfy our need for comfort, but it may stifle the soul. Becoming a famous lawyer is only worthwhile if the soul demands it. It is an essential failure if you are called to be a monastic this time around. If you need to explore and abandon ten careers in order to stretch your soul toward its innate image, then so be it. Flake it till you make it.

blog.bryanroessler.com/_posts/2020-02-28-sample-markdown.md

@@ -0,0 +1,95 @@
+---
+layout: post
+title: Sample blog post to learn markdown tips
+subtitle: There's lots to learn!
+gh-repo: daattali/beautiful-jekyll
+gh-badge: [star, fork, follow]
+tags: [test]
+comments: true
+mathjax: true
+author: Bill Smith
+---
+
+{: .box-success}
+This is a demo post to show you how to write blog posts with markdown.  I strongly encourage you to [take 5 minutes to learn how to write in markdown](https://markdowntutorial.com/) - it'll teach you how to transform regular text into bold/italics/tables/etc.<br/>I also encourage you to look at the [code that created this post](https://raw.githubusercontent.com/daattali/beautiful-jekyll/master/_posts/2020-02-28-sample-markdown.md) to learn some more advanced tips about using markdown in Beautiful Jekyll.
+
+**Here is some bold text**
+
+## Here is a secondary heading
+
+[This is a link to a different site](https://deanattali.com/) and [this is a link to a section inside this page](#local-urls).
+
+Here's a table:
+
+| Number | Next number | Previous number |
+| :------ |:--- | :--- |
+| Five | Six | Four |
+| Ten | Eleven | Nine |
+| Seven | Eight | Six |
+| Two | Three | One |
+
+You can use [MathJax](https://www.mathjax.org/) to write LaTeX expressions. For example:
+When \\(a \ne 0\\), there are two solutions to \\(ax^2 + bx + c = 0\\) and they are $$x = {-b \pm \sqrt{b^2-4ac} \over 2a}.$$
+
+How about a yummy crepe?
+
+![Crepe](https://beautifuljekyll.com/assets/img/crepe.jpg)
+
+It can also be centered!
+
+![Crepe](https://beautifuljekyll.com/assets/img/crepe.jpg){: .mx-auto.d-block :}
+
+Here's a code chunk:
+
+~~~
+var foo = function(x) {
+  return(x + 5);
+}
+foo(3)
+~~~
+
+And here is the same code with syntax highlighting:
+
+```javascript
+var foo = function(x) {
+  return(x + 5);
+}
+foo(3)
+```
+
+And here is the same code yet again but with line numbers:
+
+{% highlight javascript linenos %}
+var foo = function(x) {
+  return(x + 5);
+}
+foo(3)
+{% endhighlight %}
+
+## Boxes
+You can add notification, warning and error boxes like this:
+
+### Notification
+
+{: .box-note}
+**Note:** This is a notification box.
+
+### Warning
+
+{: .box-warning}
+**Warning:** This is a warning box.
+
+### Error
+
+{: .box-error}
+**Error:** This is an error box.
+
+## Local URLs in project sites {#local-urls}
+
+When hosting a *project site* on GitHub Pages (for example, `https://USERNAME.github.io/MyProject`), URLs that begin with `/` and refer to local files may not work correctly due to how the root URL (`/`) is interpreted by GitHub Pages. You can read more about it [in the FAQ](https://beautifuljekyll.com/faq/#links-in-project-page). To demonstrate the issue, the following local image will be broken **if your site is a project site:**
+
+![Crepe](/assets/img/crepe.jpg)
+
+If the above image is broken, then you'll need to follow the instructions [in the FAQ](https://beautifuljekyll.com/faq/#links-in-project-page). Here is proof that it can be fixed:
+
+![Crepe]({{ '/assets/img/crepe.jpg' | relative_url }})

blog.bryanroessler.com/_posts/2020-03-18-insert-code-blocks-from-repository.md

@@ -0,0 +1,55 @@
+---
+layout: post
+title: Implementing dynamic code blocks in jekyll using liquid tags
+subtitle: Keep your tutorials in sync with upstream code
+#bigimg: /img/path.jpg
+tags: [jekyll, ruby, liquid, tags, git]
+---
+
+### Overview
+
+Blogs are a great way to share code with users searching for solutions to similar problems. However, most code is ever-evolving, and as any programmer will tell you, "code is only finished when it is abandoned." Writing static journal entries containing copy-and-pasted code blocks will lead to divergence from your code repositories as you continue to improve your software.
+
+**Wouldn't it be great if your blog's code blocks could dynamically track the code residing in your version control repository?**
+
+### Github, Gogs, and GitLab
+
+If you are using Github to host your code, there are likely plenty of existing third-party solutions for updating your code blocks in your blogging platform. If you find that the existing solutions do not work then you can also use a similar solution to the one I provide here using [ruby](https://www.ruby-lang.org/en/) and [jekyll](https://jekyllrb.com/). I prefer self-hosting my code using lightweight [gogs](https://gogs.io/) while others prefer [Gitlab](https://about.gitlab.com/) or the myriad other repository solutions that may not have existing third-party solutions for dynamic code blocks.
+
+### Jekyll and other blogging platforms
+
+In this example I will be using jekyll, a lightweight blogging platform built on ruby. Generally, ruby is an easy web language to write and understand with some deficiencies in documentation and debugging, which is why I would like to provide more ready-made solutions to common problems. I generally prefer [python](https://www.python.org/) for most projects but the existing functionality provided by ruby out-of-the-box for web development still outpaces [django](https://www.djangoproject.com/). If you are using a different platform and/or framework then you may be able to adapt my admittedly simple ruby solution to whichever language you require.
+
+### `insert_git_here` ruby plugin
+
+If you are using jekyll to build the site you wish to contain dynamic code blocks, ruby plugins will be read in automatically from the `_plugins` directory located in the root of your build.
+
+**Note:** The `github-pages` gem disallows loading ruby plugins from the `_plugins` directory by default. In this case, you will need to set set the env `DISABLE_WHITELIST=true` or remove `github-pages` and replace it with the vanilla `jekyll` gem in your Gemfile.
+
+In `_plugins`, create the following file:
+
+[insert_git_code.rb](https://git.bryanroessler.com/bryan/www/raw/master/blog.bryanroessler.com/_plugins/insert_git_code.rb)
+
+{% highlight ruby %}
+{% insert_git_code https://git.bryanroessler.com/bryan/www/raw/master/blog.bryanroessler.com/_plugins/insert_git_code.rb %}
+{% endhighlight %}
+
+This is a fairly simple Liquid tags plugin that just returns the text in a raw text file from a url.
+
+### Using your tag
+
+In your markdown post or page, include something similar to the following (which is the code verbatim I used to display the dynamic code block shown above):
+
+{% highlight markdown %}
+{{ "{% highlight ruby " }}%}
+{{ "{% insert_git_code https://git.bryanroessler.com/bryan/www/raw/master/blog.bryanroessler.com/_plugins/insert_git_code.rb " }}%}
+{{ "{% endhighlight " }}%}
+{% endhighlight %}
+
+I'm actually using the plugin to display the `insert_git_code.rb` code block above, so if you can see it you can be guaranteed that the plugin is functional.
+
+You can always change the highlighting implementation to match your dynamic code block. The next steps are to add line number slicing for code snippet support, display a link to download the script automatically, error checking, and improving code format detection. By the time that you read this maybe some of these features will have already been implemented in the `insert_git_code` dynamic code block above! Just remember that you will need to restart jekyll in order to load your new plugin (still not fixed upstream) and regenerate your site to pull your updated code.
+
+### Conclusions
+
+In this tutorial we implemented a dynamic code block using a ruby plugin and liquid tags within the jekyll web framework. This strategy can be adapted to other web frameworks in order to keep instructional blog posts in sync with upstream code.

blog.bryanroessler.com/_posts/2020-04-01-prune.md

@@ -0,0 +1,46 @@
+---
+layout: post
+title: prunefiles
+subtitle: An easy way to keep your repositories clean
+tags:
+  - prune
+  - git
+  - repositories
+  - fedora
+---
+
+## Overview
+
+Here's a simple script/function to keep *n* number of the latest files that match your argument(s) in the current directory. I wrote this in order to periodically clean rpm and deb repositories. It will create file lists by matching one or more input arguments and keep only the latest file from each list. The number of files to be kept for each matching list can be set using `-k`. The file can safely be sourced as a function.
+
+### Code
+
+[prunefiles](https://git.bryanroessler.com/bryan/scripts/raw/master/prunefiles):
+
+~~~bash
+{% insert_git_code https://git.bryanroessler.com/bryan/scripts/raw/master/prunefiles %}
+~~~
+
+### Example
+
+~~~bash
+$ ls
+Package-25-1.rpm
+Package-25-2.rpm
+Package-25-3.rpm
+Package-25-4.rpm
+Package-26-1.rpm
+Package-26-2.rpm
+Package-27-1.rpm
+Package-27-2.rpm
+$ prunefiles Package-25 Package-27
+$ ls
+Package-25-4.rpm
+Package-26-1.rpm
+Package-26-2.rpm
+Package-27-2.rpm
+~~~
+
+### Conclusion
+
+I have provided a `prunefiles` script/function that keeps *n* number of latest files in the current directory that match any number of input argument(s).

blog.bryanroessler.com/_posts/2020-05-15-podmanrun-a-simple-podman-wrapper.md

@@ -0,0 +1,93 @@
+---
+layout: post
+title: 'podmanRun'
+date: '2020-05-15 15:36'
+subtitle: A simple podman run wrapper
+tags:
+  - podman
+  - bash
+  - fedora
+  - containers
+---
+
+### Rationale
+
+[In a previous post]({% post_url 2020-01-23-run-with-podman %}) I demonstrated the benefits of running and developing code in containers in order to maintain a clean and predictable development environment. After using [run-with-podman](https://git.bryanroessler.com/bryan/run-with-podman) for several months I often ran into edge cases requiring additional argument handling. In light of this, I have simplified run-with-podman into `podmanRun`, a [podman](https://podman.io/) cli wrapper that can pass arguments directly to podman while maintaining the container management benefits of run-with-podman.
+
+### Who is `podmanRun` intended for?
+
+Anyone that wants to easily run programs in ephemeral or persistent containers. Personally, I use `podmanRun` in order to quickly test code in different Linux distributions, automate compilation, and deploy containerized build services including preprocessors and web servers.
+
+### What does `podmanRun` actually do?
+
+Not much, by design.
+
+1. Generates a unique container name based on the `--name` argument passed to `podman` within the `podmanRun` `--options` string. If no `--name` is specified in the `--options` string, podmanRun will generate a unique container name based on the concatenated options and commands passed by the user. Thus, if any options or commands are changed, a new container will be recreated regardless if `--mode=persistent` was set.
+2. Checks whether a container with that name already exists.
+3. If no matching container was found: the `--options` are passed directly to `podman run` and the commands are executed in the new container.
+4. If a matching container was found:
+
+- `--mode=recreate` will remove the existing container and run the commands in a new container using `podman run` with the provided `--options`.
+- `--mode=persistent` will run the commands in the existing container using `podman exec` and `--options` will be ignored.
+
+5. By default, the container is not removed afterwards (it will only be removed upon subsequent invocations of `podmanRun` using `--mode=recreate`) to allow the user to inspect the container. Containers can be automatically removed after execution by uncommenting the requisite line in `__main()`.
+
+### Usage
+
+For the complete list of up-to-date options, run `podmanRun --help`.
+
+```bash
+podmanRun [-m MODE] [-o OPTIONS] [COMMANDS [ARGS]...] [--help] [--debug]
+```
+
+#### Options
+
+```text
+--mode, -m MODE
+    1. recreate (default) (remove container if it already exists and create a new one)
+    2. persistent (reuse existing container if it exists)
+--options, -o OPTIONS
+    OPTIONS to pass to podman run/exec
+--debug, -d
+    Print debugging
+--help, -h
+    Print this help message and exit
+```
+
+`podmanRun` supports two modes: `recreate` and `persistent`. Recreate will always overwrite an existing container with the same name, while persistent will try to execute commands in an existing container (if found) using `podman exec`.
+
+Podman options can be passed to `--options` as a single string to be split on whitespace or passed multiple times discretely.
+
+##### Examples
+
+Run an ephemeral PHP webserver container using the current directory as webroot:
+
+```shell
+podmanRun -o "-p=8000:80 --name=php_script -v=$PWD:/var/www/html:z php:7.3-apache"
+```
+
+Run an ephemeral PHP webserver container using the current directory as webroot using IDE:
+
+```shell
+podmanRun -o "-p=8000:80 --name=php_{FILE_ACTIVE_NAME_BASE} -v={FILE_ACTIVE_PATH}:/var/www/html:z php:7.3-apache"
+```
+
+Run an ephemeral bash script:
+
+```sehll
+podmanRun -o "--name=bash_script -v=$PWD:$PWD:z -w=$PWD debian:testing" ./script.sh
+```
+
+Run an ephemeral bash script using IDE:
+
+```sehll
+podmanRun -o "--name=bash_{FILE_ACTIVE_NAME_BASE}" \
+          -o "-v={FILE_ACTIVE_PATH}:{FILE_ACTIVE_PATH}:z" \
+          -o "-w={FILE_ACTIVE_PATH}" \
+          -o "debian:testing" \
+          {FILE_ACTIVE} arg1 arg2
+```
+
+## Additional Info
+
+Did you find `podmanRun` useful? [Buy me a coffee!](https://paypal.me/bryanroessler?locale.x=en_US)

blog.bryanroessler.com/_posts/2020-12-14-btrfs-on-wsl2.md

@@ -0,0 +1,111 @@
+---
+layout: post
+title: 'BTRFS on WSL2'
+date: '2020-12-14 15:36'
+subtitle: It works
+tags:
+  - BTRFS
+  - wsl2
+  - windows
+  - fedora
+---
+
+
+### Introduction
+
+Recently I needed to move 20TB worth of data stored on my last remaining Windows HTPC server over to a BTRFS-powered NAS running a *BTRFSized* Fedora 33. However, I was quite limited by the wi-fi speeds of the embedded server running the data array and benchmarks indicated it would take several days to complete. Instead of moving displays around, I figured I would see if it was possible to connect the BTRFS drive array directly to the Windows server using WSL2. Of course, such a situation would've been unthinkable a year ago, but now thanks to the ability to use a full Linux kernel in WSL2, the process is relatively simple as long as you are willing to upgrade to a bleeding edge Windows 10 developer edition to enable the ability to mount block devices in WSL2.
+
+### WSL2
+
+In version 2 of the Windows Subsystem for Linux (WSL2), Microsoft started shipping a full linux kernel on top of its virtualization stack. Since BTRFS is baked into recent Linux kernels, suddenly these "Linux-only" filesystems could now be used on Windows via the WSL2. Unfortunately it was still impossible to interact with hardware block devices (and thus mount multi-drive BTRFS device arrays) until Windows 10 [Build 20211](https://docs.microsoft.com/en-us/windows/wsl/release-notes), which is still a preview build. This means you will need to enable some Microsoft telemetry, join their Insider Program (their unpaid beta testing team), and upgrade to the latest developer build to enable the `wsl --mount` feature. Since this will be the *coup d'état* for this server, I don't worry much about the long-term privacy concerns or stability risks. If this is not the case for you, **it may be a good idea to wait** until all of these awesome features trickle down to more stable builds.
+
+1. Upgrade to a Windows Build >= 20211 by joining the Insider Program from the Windows settings (entails several reboots)
+
+Additional steps I had to perform in Windows:
+
+1. Enable WSL2 VM support: `dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart`
+2. Set my default WSL to version 2: `wsl --set-default-version 2`
+3. If you have an existing WSL installation, you will need to convert it from WSL1 to WSL2: `wsl --set-version Ubuntu 2`
+
+### The array
+
+The BTRFS array consists of 5 disks in a **RAID1c3** configuration that was created on a Fedora 33 server. So-called "3-Copy" support was added to **Linux 5.5** and adds some additional redundancy. Unfortunately, the WSL2 currently ships with a Linux 4.9 by default. It's possible to upgrade the kernel to some extent using [a package from Microsoft](https://docs.microsoft.com/en-us/windows/wsl/install-win10#step-4---download-the-linux-kernel-update-package), but I was still stuck on 5.4 even after installing the update package.
+
+It's certainly possible to build your own Linux kernel from Microsoft's [Linux 5.4 source repository](https://github.com/microsoft/WSL2-Linux-Kernel/tree/linux-msft-wsl-5.4.y) if you wanted to go that route. In my case the BTRFS version in the kernel would still not be able to read my RAID1c3 array.
+
+Luckily, [Nathan Chance](https://github.com/nathanchance/WSL2-Linux-Kernel) has a public repository available of WSL2-compatible Linux kernels tracking upstream. You can build it using his toolchain or use one of his latest pre-compiled [releases](https://github.com/nathanchance/WSL2-Linux-Kernel/releases). As I mentioned earlier, I'm not too concerned with performance or security here so I'm willing to use a third-party solution to save time as this is a one-shot operation. Thanks, Nathan.
+
+After downloading the bzImage you will need to point WSL2 at the new kernel by placing a file at `C:\Users\username\.wslconfig` containing:
+
+```(text)
+[wsl2]
+kernel = C:\\Users\\username\\Downloads\\bzImage
+```
+
+Yes, those are **double slashes**, because Windows.
+
+Now you can restart your wsl instance (`wsl --shutdown`) or just reboot and you should be running a sparkling fresh kernel (confirm with `uname -a`). At the time of this writing, Linux 5.10 kernels were already available.
+
+### Passthrough the BTRFS device (or partition) to WSL2
+
+Now that our tools are up-to-date we can go ahead and mount (passthrough) our block devices and BTRFS partitions. In Windows you will need to identify the **DeviceID** of the disk(s) you wish to passthrough to WSL2 using `wmic diskdrive list brief` in an elevated prompt. In Windows fashion the nomenclature is nonsensical (probably, `\\.\PHYSICALDRIVE2`).
+
+In my case I had to passthrough all five drives in the array. WSL2 does have the ability to mount btrfs partitions directly using the `-t` option, but we will just be passing the bare drives as block devices instead:
+
+```(powershell)
+wsl --mount \\.\PHYSICALDRIVE5 --bare
+wsl --mount \\.\PHYSICALDRIVE6 --bare
+wsl --mount \\.\PHYSICALDRIVE7 --bare
+wsl --mount \\.\PHYSICALDRIVE8 --bare
+wsl --mount \\.\PHYSICALDRIVE9 --bare
+```
+
+These will all become block devices in `/dev/sd*`.
+
+### Mount the BTRFS filesystem and transfer your data
+
+After adding your drives to the WSL2, for good measure run a `sudo btrfs device scan` to make the kernel aware of their existence.
+
+Check for device blocks:
+
+```(shell)
+$ sudo blkid
+/dev/sda: UUID="3255683f-53a2-4fdf-91cf-b4c1041e2a62" TYPE="ext4"
+/dev/sdb: UUID="3255683f-53a2-4fdf-91cf-b4c1041e2a62" TYPE="ext4"
+/dev/sdc: LABEL="array" UUID="6f7065bf-3f6c-4950-b305-e5d3565b9385" UUID_SUB="bdfea478-7826-48ed-b000-04894aac221d" TYPE="btrfs"
+/dev/sdd: LABEL="array" UUID="6f7065bf-3f6c-4950-b305-e5d3565b9385" UUID_SUB="95615881-0962-4318-b04d-6aa21d991a33" TYPE="btrfs"
+/dev/sde: LABEL="array" UUID="6f7065bf-3f6c-4950-b305-e5d3565b9385" UUID_SUB="abc9baa8-4b76-4630-a1d5-e91852dca20c" TYPE="btrfs"
+/dev/sdf: LABEL="array" UUID="6f7065bf-3f6c-4950-b305-e5d3565b9385" UUID_SUB="e06ddecc-57cd-4458-a4a7-22689f940b02" TYPE="btrfs"
+/dev/sdg: LABEL="array" UUID="6f7065bf-3f6c-4950-b305-e5d3565b9385" UUID_SUB="08f00c39-b1bc-4b01-9f1d-e1efb8686fd4" TYPE="btrfs"
+```
+
+BTRFS is smart enough to mount the whole device array even when specifying a single disk member. So just create a sensible mount point and mount any of your btrfs devices: `sudo mkdir /mnt/array && sudo mount /dev/sdc /mnt/array`.
+
+`cd /mnt/array` into your mounted BTRFS array to make sure everything looks good and your subvolumes are present: `sudo btrfs subvolume list /`
+
+If everything looks good, go ahead and start transferring your data over from your Windows partitions, which are also conveniently mounted in `/mnt` (as you have probably spotted by now if you've been following along).
+
+By default the Windows filesystems are `a+rwx` so it is pretty easy to pull data from them with rsync without too many permission hassles using the `-a` archive option: `rsync -a --info=progress2 /mnt/d/media/ /mnt/e/media/ /mnt/array/media`
+
+As you can see in the above rsync command, I chose to chain several source directories together to simplify the transfer to the new array.
+
+### Cleanup
+
+After you are finished moving data around:
+
+1. Unmount the array in WSL: `sudo umount /dev/array` **Note:** Make sure you aren't currently in the mount point or you will get `target is busy` errors when trying to unmount. `cd ~` first.
+2. Back in Windows, unshare the drive with the WSL2:
+
+```(powershell)
+wsl --unmount \\.\PHYSICALDRIVE5
+wsl --unmount \\.\PHYSICALDRIVE6
+wsl --unmount \\.\PHYSICALDRIVE7
+wsl --unmount \\.\PHYSICALDRIVE8
+wsl --unmount \\.\PHYSICALDRIVE9
+```
+
+And voilà, you are done!
+
+### Conclusions
+
+Even though my aging Windows server was limited to 5 GB/s USB throughput, I was still able to complete the transfer in a matter of hours (not days) and without putting tremendous load on my network for an extended period of time. It is also perhaps bittersweet that I exit the ecosystem just as it achieves some useful level of compatibility with my preferred workflow. In theory one could even share BTRFS devices between Windows and Linux as long as they were not simultaneously mounted. Of course, in most cases it would be more sensible to use a network-based solution but for those seeking optimal performance, the WSL2 offers a compelling option.

blog.bryanroessler.com/_posts/2021-02-18-external-wsl2-access-ubuntu-20-w-powershell.md

@@ -0,0 +1,52 @@
+---
+layout: post
+title: 'Restoring external (remote) WSL2 access'
+date: 2021-02-18 11:01
+tags: [windows, wsl, wsl2, linux, ssh, firewall, ip, ifconfig, powershell]
+---
+
+## Cannot access WSL2 instances remotely
+
+If you rely on external (remote) access to the Windows Subsystem for Linux (WSL2) you may have noticed that your manual port forwards have suddenly stopped working. Microsoft has started issuing WSL2 instances a randomized IP address on startup, which makes it difficult to reliably access services hosted in the Linux subsystem. However, it's still possible to probe the WSL2 instance on startup and open the appropriate ports using Powershell.
+
+Most existing solutions rely on legacy `ifconfig`, which has been deprecated in Ubuntu 20.04 (available in WSL2 via an in-place `do-release-upgrade`) in favor of `ip`.
+
+## Allow WSL2 to bypass the Windows Firewall with a Powershell task
+
+Steps:
+
+1. [Download](https://git.bryanroessler.com/bryan/scripts/raw/master/powershell/wsl2-firewall-rules.ps1) or copy-paste the following Powershell script to a local file:
+{% highlight powershell %}
+{% insert_git_code https://git.bryanroessler.com/bryan/scripts/raw/master/powershell/wsl2-firewall-rules.ps1 %}
+{% endhighlight %}
+2. Edit the port list to add any additional WSL2 ports you wish to expose
+3. Create a startup new task in the Windows Task Scheduler:
+
+    * Name: 'WSL2-Bypass'
+    * Triggers: At log on, for any user
+    * Actions:
+        * Program/Script: `powershell`
+        * Add Arguments: `-ExecutionPolicy Bypass C:\Users\Bryan\Path\To\wsl2-firewall-rules.ps1`
+
+4. Save the task and run it
+
+## Starting WSL2 services automatically at login
+
+You can use your `.bashrc` in the WSL2 or simply append the following line to the beginning of your powershell task:
+
+`bash.exe -c "sudo /usr/sbin/service ssh start; sudo /usr/sbin/service unattended-upgrades start"`
+
+You can add or remove services as necessary. In order to be able to use root privileges without entering a password, you will need to edit the sudoers file using **`visudo`** and adding the following lines:
+
+```(bash)
+bryan ALL = NOPASSWD: /usr/sbin/service start ssh
+bryan ALL = NOPASSWD: /usr/sbin/service start unattended-upgrades
+```
+
+## Troubleshooting
+
+* Make sure that you have already made the appropriate firewall changes within the instance itself.
+* Make sure that your service is running.
+* Try probing for the IP address manually and connecting to the service from the Windows machine.
+
+Enjoy unfettered remote access to your WSL2 services again!

blog.bryanroessler.com/_posts_drafts/2015-02-28-test-markdown.md

@@ -1,73 +0,0 @@
----
-layout: post
-title: Test markdown
-subtitle: Each post also has a subtitle
-gh-repo: daattali/beautiful-jekyll
-gh-badge: [star, fork, follow]
-tags: [test]
----
-
-You can write regular [markdown](http://markdowntutorial.com/) here and Jekyll will automatically convert it to a nice webpage.  I strongly encourage you to [take 5 minutes to learn how to write in markdown](http://markdowntutorial.com/) - it'll teach you how to transform regular text into bold/italics/headings/tables/etc.
-
-**Here is some bold text**
-
-## Here is a secondary heading
-
-Here's a useless table:
-
-| Number | Next number | Previous number |
-| :------ |:--- | :--- |
-| Five | Six | Four |
-| Ten | Eleven | Nine |
-| Seven | Eight | Six |
-| Two | Three | One |
-
-
-How about a yummy crepe?
-
-![Crepe](http://s3-media3.fl.yelpcdn.com/bphoto/cQ1Yoa75m2yUFFbY2xwuqw/348s.jpg)
-
-Here's a code chunk:
-
-~~~
-var foo = function(x) {
-  return(x + 5);
-}
-foo(3)
-~~~
-
-And here is the same code with syntax highlighting:
-
-```javascript
-var foo = function(x) {
-  return(x + 5);
-}
-foo(3)
-```
-
-And here is the same code yet again but with line numbers:
-
-{% highlight javascript linenos %}
-var foo = function(x) {
-  return(x + 5);
-}
-foo(3)
-{% endhighlight %}
-
-## Boxes
-You can add notification, warning and error boxes like this:
-
-### Notification
-
-{: .box-note}
-**Note:** This is a notification box.
-
-### Warning
-
-{: .box-warning}
-**Warning:** This is a warning box.
-
-### Error
-
-{: .box-error}
-**Error:** This is an error box.

blog.bryanroessler.com/assets/css/beautifuljekyll-minimal.css

@@ -1,12 +1,12 @@
 .main-content {
-  padding-bottom: 50px;
+  padding-bottom: 3.125rem;
 }
 
 footer.footer-min {
   position: fixed;
   bottom: 0;
   width: 100%;
-  padding: 3px;
+  padding: 0.1875rem;
   background-color: #f5f5f5;
   border-top: 1px solid #eeeeee;
   text-align: center;

blog.bryanroessler.com/assets/css/pygment_highlights.css

@@ -59,8 +59,3 @@
 .highlight .vg { color: #008080 } /* Name.Variable.Global */
 .highlight .vi { color: #008080 } /* Name.Variable.Instance */
 .highlight .il { color: #009999 } /* Literal.Number.Integer.Long */
-
-/* Make line numbers unselectable: excludes line numbers from copy-paste user ops */
-.highlight .lineno {color:rgba(0,0,0,0.3);padding: 0 10px;-webkit-user-select: none;-moz-user-select: none; -o-user-select: none;}
-.lineno::-moz-selection {background-color: transparent;} /* Mozilla specific */
-.lineno::selection {background-color: transparent;} /* Other major browsers */

blog.bryanroessler.com/assets/css/staticman.css

@@ -0,0 +1,180 @@
+/* ==========================================================================
+ Forms
+ ========================================================================== */
+.staticman-comments form {
+  margin: 0 0 5px 0;
+  padding: 1em;
+  background-color: #f2f3f3;
+}
+.staticman-comments form p {
+  margin-bottom: 2.5px;
+}
+.staticman-comments form br {
+  display: none;
+}
+.staticman-comments label, .staticman-comments input, .staticman-comments button, .staticman-comments textarea {
+  vertical-align: baseline;
+  vertical-align: middle;
+}
+.staticman-comments input, .staticman-comments button, .staticman-comments textarea {
+  box-sizing: border-box;
+}
+.staticman-comments label {
+  display: block;
+  margin-bottom: 0.25em;
+  color: #494e52;
+  cursor: pointer;
+}
+.staticman-comments label small {
+  font-size: 0.75em;
+}
+.staticman-comments label input, .staticman-comments label textarea {
+  display: block;
+}
+.staticman-comments input, .staticman-comments textarea {
+  display: inline-block;
+  width: 100%;
+  padding: 0.25em;
+  margin-bottom: 0.5em;
+  color: #494e52;
+  background-color: #fff;
+  border: #f2f3f3;
+  border-radius: 4px;
+  box-shadow: 0 1px 1px rgba(0, 0, 0, 0.125);
+}
+.staticman-comments .input-mini {
+  width: 60px;
+}
+.staticman-comments .input-small {
+  width: 90px;
+}
+.staticman-comments input[type="button"], .staticman-comments input[type="reset"], .staticman-comments input[type="submit"] {
+  width: auto;
+  height: auto;
+  cursor: pointer;
+  overflow: visible;
+}
+.staticman-comments textarea {
+  resize: vertical;
+  height: auto;
+  overflow: auto;
+  vertical-align: top;
+}
+.staticman-comments input[type="hidden"] {
+  display: none;
+}
+.staticman-comments .form {
+  position: relative;
+}
+/*
+ Focus & active state
+ ========================================================================== */
+.staticman-comments input:focus, .staticman-comments textarea:focus {
+  border-color: #7a8288;
+  outline: 0;
+  outline: thin dotted \9;
+  box-shadow: inset 0 1px 3px rgba(73, 78, 82, 0.06), 0 0 5px rgba(122, 130, 136, 0.7);
+}
+.staticman-comments input[type="file"]:focus, .staticman-comments input[type="radio"]:focus, .staticman-comments input[type="checkbox"]:focus:focus {
+  box-shadow: none;
+}
+/*
+ Help text
+ ========================================================================== */
+.staticman-comments .form-text {
+  color: #898c8e;
+}
+.staticman-comments .form-text {
+  display: block;
+  margin-bottom: 1em;
+  line-height: 1em;
+}
+/*
+ .form-group
+ ========================================================================== */
+.staticman-comments .form-group {
+  margin-bottom: 5px;
+  padding: 0;
+  border-width: 0;
+}
+/*
+ Comments
+ ========================================================================== */
+.staticman-comments .page__comments {
+  float: left;
+  margin-left: 0;
+  margin-right: 0;
+  width: 100%;
+  clear: both;
+}
+.staticman-comments .page__comments-title {
+  margin-top: 2rem;
+  margin-bottom: 10px;
+  padding-top: 2rem;
+  border-top: 1px solid #f2f3f3;
+}
+.staticman-comments .page__comments-form {
+  -webkit-transition: all 0.2s ease-in-out;
+  transition: all 0.2s ease-in-out;
+}
+.staticman-comments .page__comments-form.disabled input, .staticman-comments .page__comments-form.disabled button, .staticman-comments .page__comments-form.disabled textarea, .staticman-comments .page__comments-form.disabled label {
+  pointer-events: none;
+  cursor: not-allowed;
+  filter: alpha(opacity=65);
+  box-shadow: none;
+  opacity: 0.65;
+}
+.staticman-comments .comment {
+  margin: 1em 0;
+}
+.staticman-comments .comment:not(:last-child) {
+  border-bottom: 1px solid #f2f3f3;
+}
+.staticman-comments .comment__avatar-wrapper {
+  float: left;
+  width: 60px;
+  height: 60px;
+}
+.staticman-comments .comment__avatar {
+  width: 40px;
+  height: 40px;
+  border-radius: 50%;
+}
+.staticman-comments .comment__content-wrapper {
+  width: calc(100% - 60px);
+}
+.staticman-comments .comment__author {
+  margin: 0;
+}
+.staticman-comments .comment__author a {
+  text-decoration: none;
+}
+.staticman-comments .comment__date {
+  margin: 0;
+}
+.staticman-comments .comment__date a {
+  text-decoration: none;
+}
+/* ==========================================================================
+ PRINT STYLES
+ ========================================================================== */
+.staticman-comments @media print {
+  /*
+   Hide the following elements on print
+   ========================================================================== */
+.staticman-comments [hidden] {
+    display: none;
+  }
+.staticman-comments .masthead, .staticman-comments .toc, .staticman-comments .page__share, .staticman-comments .page__related, .staticman-comments .pagination, .staticman-comments .ads, .staticman-comments .page__footer, .staticman-comments .page__comments-form, .staticman-comments .author__avatar, .staticman-comments .author__content, .staticman-comments .author__urls-wrapper, .staticman-comments .nav__list, .staticman-comments .sidebar, .staticman-comments .adsbygoogle {
+    display: none !important;
+    height: 1px !important;
+  }
+}
+/*
+ Post pagination navigation links
+ ========================================================================== */
+.staticman-comments .page__comments + .staticman-comments .pagination {
+  margin-top: 2em;
+  padding-top: 2em;
+  border-top: 1px solid #f2f3f3;
+}

blog.bryanroessler.com/assets/data/searchcorpus.json

@@ -0,0 +1,23 @@
+---
+layout: null
+---
+[ 
+{% for post in site.posts %} 
+{ 
+"title"    : "{% if post.title != "" %}{{ post.title | strip_html | escape }}{% else %}{{ post.excerpt | strip_html | escape | strip }}{%endif%}", 
+"desc"     : "{% if post.title != "" %}{{ post.title | strip_html | escape }}{% else %}{{ post.excerpt | strip_html | escape | strip }}{%endif%}", 
+"category" : "{{ post.tags | join: ', ' }}", 
+"url"      : "{{ site.baseurl }}{{ post.url | escape }}", 
+"date"     : "{{ post.date | date: "%B %e, %Y" | default: "January 1, 1970" }}" 
+}, 
+{% endfor %} 
+{% for page in site.html_pages %}{% if page.title != "{title}" and page.title != "404 - Page not found" %} 
+{ 
+"title"    : "{% if page.title != "" %}{{ page.title | strip_html | escape }}{% else %}{{ page.excerpt | strip_html | escape | strip }}{% endif %}", 
+"desc"     : "{% if page.title != "" %}{{ page.title | strip_html | escape }}{% else %}{{ page.excerpt | strip_html | escape | strip }}{% endif %}", 
+"category" : "{% if page.tags %}{{ page.tags | join: ', ' }}{% else %}page{% endif %}", 
+"url"      : "{{ site.baseurl }}{{ page.url }}", 
+"date"     : "{{ page.date | date: '%B %e, %Y' | default: "January 1, 1970" }}" 
+}{% unless forloop.last %},{% endunless %} 
+{% endif %}{% endfor %} 
+]

blog.bryanroessler.com/assets/js/beautifuljekyll.js

@@ -0,0 +1,142 @@
+// Dean Attali / Beautiful Jekyll 2023
+
+let BeautifulJekyllJS = {
+
+  bigImgEl : null,
+  numImgs : null,
+
+  init : function() {
+    setTimeout(BeautifulJekyllJS.initNavbar, 10);
+
+    // Shorten the navbar after scrolling a little bit down
+    $(window).scroll(function() {
+        if ($(".navbar").offset().top > 50) {
+            $(".navbar").addClass("top-nav-short");
+        } else {
+            $(".navbar").removeClass("top-nav-short");
+        }
+    });
+
+    // On mobile, hide the avatar when expanding the navbar menu
+    $('#main-navbar').on('show.bs.collapse', function () {
+      $(".navbar").addClass("top-nav-expanded");
+    });
+    $('#main-navbar').on('hidden.bs.collapse', function () {
+      $(".navbar").removeClass("top-nav-expanded");
+    });
+
+    // show the big header image
+    BeautifulJekyllJS.initImgs();
+
+    BeautifulJekyllJS.initSearch();
+  },
+
+  initNavbar : function() {
+    // Set the navbar-dark/light class based on its background color
+    const rgb = $('.navbar').css("background-color").replace(/[^\d,]/g,'').split(",");
+    const brightness = Math.round(( // http://www.w3.org/TR/AERT#color-contrast
+      parseInt(rgb[0]) * 299 +
+      parseInt(rgb[1]) * 587 +
+      parseInt(rgb[2]) * 114
+    ) / 1000);
+    if (brightness <= 125) {
+      $(".navbar").removeClass("navbar-light").addClass("navbar-dark");
+    } else {
+      $(".navbar").removeClass("navbar-dark").addClass("navbar-light");
+    }
+  },
+
+  initImgs : function() {
+    // If the page was large images to randomly select from, choose an image
+    if ($("#header-big-imgs").length > 0) {
+      BeautifulJekyllJS.bigImgEl = $("#header-big-imgs");
+      BeautifulJekyllJS.numImgs = BeautifulJekyllJS.bigImgEl.attr("data-num-img");
+
+      // 2fc73a3a967e97599c9763d05e564189
+      // set an initial image
+      const imgInfo = BeautifulJekyllJS.getImgInfo();
+      const src = imgInfo.src;
+      const desc = imgInfo.desc;
+      BeautifulJekyllJS.setImg(src, desc);
+
+      // For better UX, prefetch the next image so that it will already be loaded when we want to show it
+      const getNextImg = function() {
+        const imgInfo = BeautifulJekyllJS.getImgInfo();
+        const src = imgInfo.src;
+        const desc = imgInfo.desc;
+
+        const prefetchImg = new Image();
+        prefetchImg.src = src;
+        // if I want to do something once the image is ready: `prefetchImg.onload = function(){}`
+
+        setTimeout(function(){
+          const img = $("<div></div>").addClass("big-img-transition").css("background-image", 'url(' + src + ')');
+          $(".intro-header.big-img").prepend(img);
+          setTimeout(function(){ img.css("opacity", "1"); }, 50);
+
+          // after the animation of fading in the new image is done, prefetch the next one
+          //img.one("transitioned webkitTransitionEnd oTransitionEnd MSTransitionEnd", function(){
+          setTimeout(function() {
+            BeautifulJekyllJS.setImg(src, desc);
+            img.remove();
+            getNextImg();
+          }, 1000);
+          //});
+        }, 6000);
+      };
+
+      // If there are multiple images, cycle through them
+      if (BeautifulJekyllJS.numImgs > 1) {
+        getNextImg();
+      }
+    }
+  },
+
+  getImgInfo : function() {
+    const randNum = Math.floor((Math.random() * BeautifulJekyllJS.numImgs) + 1);
+    const src = BeautifulJekyllJS.bigImgEl.attr("data-img-src-" + randNum);
+    const desc = BeautifulJekyllJS.bigImgEl.attr("data-img-desc-" + randNum);
+
+    return {
+      src : src,
+      desc : desc
+    }
+  },
+
+  setImg : function(src, desc) {
+    $(".intro-header.big-img").css("background-image", 'url(' + src + ')');
+    if (typeof desc !== typeof undefined && desc !== false) {
+      $(".img-desc").text(desc).show();
+    } else {
+      $(".img-desc").hide();
+    }
+  },
+
+  initSearch : function() {
+    if (!document.getElementById("beautifuljekyll-search-overlay")) {
+      return;
+    }
+
+    $("#nav-search-link").click(function(e) {
+      e.preventDefault();
+      $("#beautifuljekyll-search-overlay").show();
+      $("#nav-search-input").focus().select();
+      $("body").addClass("overflow-hidden");
+    });
+    $("#nav-search-exit").click(function(e) {
+      e.preventDefault();
+      $("#beautifuljekyll-search-overlay").hide();
+      $("body").removeClass("overflow-hidden");
+    });
+    $(document).on('keyup', function(e) {
+      if (e.key == "Escape") {
+        $("#beautifuljekyll-search-overlay").hide();
+        $("body").removeClass("overflow-hidden");
+      }
+    });
+  }
+};
+
+// 2fc73a3a967e97599c9763d05e564189
+
+document.addEventListener('DOMContentLoaded', BeautifulJekyllJS.init);

blog.bryanroessler.com/assets/js/staticman.js

@@ -0,0 +1,65 @@
+---
+layout: null
+---
+
+(function ($) {
+  $('#new_comment').submit(function () {
+    const form = this;
+
+    $(form).addClass('disabled');
+
+    {% assign sm = site.staticman -%}
+    const endpoint = '{{ sm.endpoint }}';
+    const repository = '{{ sm.repository }}';
+    const branch = '{{ sm.branch }}';
+    const url = endpoint + repository + '/' + branch + '/comments';
+    const data = $(this).serialize();
+
+    const xhr = new XMLHttpRequest();
+    xhr.open("POST", url);
+    xhr.setRequestHeader('Content-Type', 'application/x-www-form-urlencoded');
+    xhr.setRequestHeader('X-Requested-With', 'XMLHttpRequest');
+    xhr.onreadystatechange = function () {
+      if(xhr.readyState === XMLHttpRequest.DONE) {
+        const status = xhr.status;
+        if (status >= 200 && status < 400) {
+          formSubmitted();
+        } else {
+          formError();
+        }
+      }
+    };
+
+    function formSubmitted() {
+      $('#comment-form-submit').addClass('d-none');
+      $('#comment-form-submitted').removeClass('d-none');
+      $('.page__comments-form .js-notice').removeClass('alert-danger');
+      $('.page__comments-form .js-notice').addClass('alert-success');
+      showAlert('success');
+    }
+
+    function formError() {
+      $('#comment-form-submitted').addClass('d-none');
+      $('#comment-form-submit').removeClass('d-none');
+      $('.page__comments-form .js-notice').removeClass('alert-success');
+      $('.page__comments-form .js-notice').addClass('alert-danger');
+      showAlert('failure');
+      $(form).removeClass('disabled');
+    }
+
+    xhr.send(data);
+
+    return false;
+  });
+
+  function showAlert(message) {
+    $('.page__comments-form .js-notice').removeClass('d-none');
+    if (message == 'success') {
+      $('.page__comments-form .js-notice-text-success').removeClass('d-none');
+      $('.page__comments-form .js-notice-text-failure').addClass('d-none');
+    } else {
+      $('.page__comments-form .js-notice-text-success').addClass('d-none');
+      $('.page__comments-form .js-notice-text-failure').removeClass('d-none');
+    }
+  }
+})(jQuery);

blog.bryanroessler.com/beautiful-jekyll-theme.gemspec

@@ -0,0 +1,30 @@
+# frozen_string_literal: true
+
+Gem::Specification.new do |spec|
+  spec.name          = "beautiful-jekyll-theme"
+  spec.version       = "6.0.1"
+  spec.authors       = ["Dean Attali"]
+  spec.email         = ["daattali@gmail.com"]
+
+  spec.summary       = "Beautiful Jekyll is a ready-to-use Jekyll theme to help you create an awesome website quickly. Perfect for personal blogs or simple project websites, with a focus on responsive and clean design."
+  spec.homepage      = "https://beautifuljekyll.com"
+  spec.license       = "MIT"
+
+  spec.files         = `git ls-files -z`.split("\x0").select { |f| f.match(%r{^(assets|_layouts|_includes|LICENSE|README|feed|404|_data|tags|staticman)}i) }
+
+  spec.metadata      = {
+    "changelog_uri"     => "https://beautifuljekyll.com/updates/",
+    "documentation_uri" => "https://github.com/daattali/beautiful-jekyll#readme"
+  }
+
+  spec.add_runtime_dependency "jekyll", ">= 3.9.3"
+  spec.add_runtime_dependency "jekyll-paginate", "~> 1.1"
+  spec.add_runtime_dependency "jekyll-sitemap", "~> 1.4"
+  spec.add_runtime_dependency "kramdown-parser-gfm", "~> 1.1"
+  spec.add_runtime_dependency "kramdown", "~> 2.3"
+  spec.add_runtime_dependency "webrick", "~> 1.8"
+
+  spec.add_development_dependency "bundler", ">= 1.16"
+  spec.add_development_dependency "rake", "~> 12.0"
+  spec.add_development_dependency "appraisal", "~> 2.5"
+end

blog.bryanroessler.com/build.sh

@@ -0,0 +1,23 @@
+#!/usr/bin/env bash
+
+# build and deploy
+#podman build \
+#    --rm \
+#    -it \
+#    -v "$PWD:/srv/jekyll" \
+#    -v "$PWD/vendor/bundle:/usr/local/bundle" \
+#    -u 1000:1001 \
+#    jekyll:latest \
+#    bundle update
+
+podman build -t atomjekylltemp "$1"
+podman run \
+    --rm \
+    -it \
+    -p 4000:4000 \
+    -v "${1}:/srv/jekyll" \
+    -v "${1}/vendor/bundle:/usr/local/bundle" \
+    localhost/atomjekylltemp \
+    /bin/bash
+
+#podman rmi localhost/atomjekylltemp

blog.bryanroessler.com/css/main.css

@@ -13,7 +13,7 @@ body {
   position: relative;
   background-color: {{ site.page-col }};
   {% if site.page-img %}
-  background-image: url({{ site.page-img }});
+  background-image: url({{ site.page-img | relative_url }});
   background-attachment: fixed;
   {% endif %}
 }
@@ -110,7 +110,7 @@ img {
   border-bottom: 1px solid #EAEAEA;
   font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif;
   {% if site.navbar-img %}
-  background-image: url({{ site.navbar-img }});
+  background-image: url({{ site.navbar-img | relative_url }});
   background-attachment: fixed;
   {% endif %}
 }
@@ -267,7 +267,7 @@ footer {
   font-size: 14px;
   background-color: {{ site.footer-col }};
   {% if site.footer-img %}
-  background-image: url({{ site.footer-img }});
+  background-image: url({{ site.footer-img | relative_url }});
   background-attachment: fixed;
   {% endif %}
 }
@@ -668,37 +668,43 @@ pre {
   font-size: 16px;
   line-height: 1.5em;
 }
-pre code {
-  white-space: pre;
-}
-pre.highlight, .highlight > pre, td.code pre {
-  background-color: #FAFAFA;
-  background-image: linear-gradient(#F9F9F9 50%, #FDFDFD 50%);
-  background-repeat: repeat;
-  background-size: 3em 3em;
-  background-position: 0px 10px;
-  border-left: 7px solid #444;
-}
-code table, code table td, code table th, code table tbody, code table tr,
-td.gutter pre {
-  padding: 0;
+.highlight pre {
   border: none;
-  background-color: #fff;
+  background: none;
+  margin: 0;
 }
 .highlight > pre {
+  background-image: linear-gradient(
+    rgba(0,0,0,0.06), rgba(0,0,0,0.06) 1.5em, rgba(0,0,0,0.03) 1.5em, rgba(0,0,0,0.03) 3em);
+  background-size: auto 3em;
+  background-position-y: 10px;
+  border: 1px solid rgba(0,0,0,0.1);
+  border-left: 7px solid #444;
+}
+.highlight > pre:not([class~="highlight"]) { /* code block with line number */
   padding: 0;
 }
-.highlight > pre.highlight {
-  padding: 9.5px;
+.highlight table, .highlight tr, .highlight td { /* to be removed after fixing table styles */
+  border: none;
+  background: none;
+  padding: 0;
+  margin: 0;
 }
-td.code pre {
-  border-width: 0 0 0 2px;
-  border-style: solid;
-  border-color: #444;
+.highlight pre.lineno {
+  color: rgba(0,0,0,0.3);
   border-radius: 0;
+  border-right: 2px solid #444;
 }
-td.gutter {
-  padding-top: 3px;
+
+/* Make line numbers unselectable: excludes line numbers from copy-paste user ops */
+.lineno {
+  -webkit-user-select: none;
+     -moz-user-select: none;
+      -ms-user-select: none;
+          user-select: none;
+}
+.lineno::selection, .lineno::-moz-selection {
+  background: none;
 }
 
 /* --- Social media sharing section --- */
@@ -708,7 +714,7 @@ td.gutter {
 }
 
 /* --- Notification boxes --- */
-.box-note, .box-warning, .box-error {
+.box-note, .box-warning, .box-error, .box-success {
   padding: 15px 15px 15px 10px;
   margin: 20px 20px 20px 5px;
   border: 1px solid #eee;
@@ -731,6 +737,11 @@ td.gutter {
   border-left-color: #c0392b;
 }
 
+.box-success {
+  background-color: #98FB98;
+  border-left-color: #3CB371;
+}
+
 /* Fix table border github gist snippets */
 
 .gist, .gist-file table tr {

blog.bryanroessler.com/css/pygment_highlights.css

@@ -59,8 +59,3 @@
 .highlight .vg { color: #008080 } /* Name.Variable.Global */
 .highlight .vi { color: #008080 } /* Name.Variable.Instance */
 .highlight .il { color: #009999 } /* Literal.Number.Integer.Long */
-
-/* Make line numbers unselectable: excludes line numbers from copy-paste user ops */
-.highlight .lineno {color:rgba(0,0,0,0.3);padding: 0 10px;-webkit-user-select: none;-moz-user-select: none; -o-user-select: none;}
-.lineno::-moz-selection {background-color: transparent;} /* Mozilla specific */
-.lineno::selection {background-color: transparent;} /* Other major browsers */

blog.bryanroessler.com/css/staticman.css

@@ -0,0 +1,180 @@
+/* ==========================================================================
+ Forms
+ ========================================================================== */
+.staticman-comments form {
+  margin: 0 0 5px 0;
+  padding: 1em;
+  background-color: #f2f3f3;
+}
+.staticman-comments form p {
+  margin-bottom: 2.5px;
+}
+.staticman-comments form br {
+  display: none;
+}
+.staticman-comments label, .staticman-comments input, .staticman-comments button, .staticman-comments textarea {
+  vertical-align: baseline;
+  vertical-align: middle;
+}
+.staticman-comments input, .staticman-comments button, .staticman-comments textarea {
+  box-sizing: border-box;
+}
+.staticman-comments label {
+  display: block;
+  margin-bottom: 0.25em;
+  color: #494e52;
+  cursor: pointer;
+}
+.staticman-comments label small {
+  font-size: 0.75em;
+}
+.staticman-comments label input, .staticman-comments label textarea {
+  display: block;
+}
+.staticman-comments input, .staticman-comments textarea {
+  display: inline-block;
+  width: 100%;
+  padding: 0.25em;
+  margin-bottom: 0.5em;
+  color: #494e52;
+  background-color: #fff;
+  border: #f2f3f3;
+  border-radius: 4px;
+  box-shadow: 0 1px 1px rgba(0, 0, 0, 0.125);
+}
+.staticman-comments .input-mini {
+  width: 60px;
+}
+.staticman-comments .input-small {
+  width: 90px;
+}
+.staticman-comments input[type="button"], .staticman-comments input[type="reset"], .staticman-comments input[type="submit"] {
+  width: auto;
+  height: auto;
+  cursor: pointer;
+  overflow: visible;
+}
+.staticman-comments textarea {
+  resize: vertical;
+  height: auto;
+  overflow: auto;
+  vertical-align: top;
+}
+.staticman-comments input[type="hidden"] {
+  display: none;
+}
+.staticman-comments .form {
+  position: relative;
+}
+/*
+ Focus & active state
+ ========================================================================== */
+.staticman-comments input:focus, .staticman-comments textarea:focus {
+  border-color: #7a8288;
+  outline: 0;
+  outline: thin dotted \9;
+  box-shadow: inset 0 1px 3px rgba(73, 78, 82, 0.06), 0 0 5px rgba(122, 130, 136, 0.7);
+}
+.staticman-comments input[type="file"]:focus, .staticman-comments input[type="radio"]:focus, .staticman-comments input[type="checkbox"]:focus:focus {
+  box-shadow: none;
+}
+/*
+ Help text
+ ========================================================================== */
+.staticman-comments .help-block {
+  color: #898c8e;
+}
+.staticman-comments .help-block {
+  display: block;
+  margin-bottom: 1em;
+  line-height: 1em;
+}
+/*
+ .form-group
+ ========================================================================== */
+.staticman-comments .form-group {
+  margin-bottom: 5px;
+  padding: 0;
+  border-width: 0;
+}
+/*
+ Comments
+ ========================================================================== */
+.staticman-comments .page__comments {
+  float: left;
+  margin-left: 0;
+  margin-right: 0;
+  width: 100%;
+  clear: both;
+}
+.staticman-comments .page__comments-title {
+  margin-top: 2rem;
+  margin-bottom: 10px;
+  padding-top: 2rem;
+  border-top: 1px solid #f2f3f3;
+}
+.staticman-comments .page__comments-form {
+  -webkit-transition: all 0.2s ease-in-out;
+  transition: all 0.2s ease-in-out;
+}
+.staticman-comments .page__comments-form.disabled input, .staticman-comments .page__comments-form.disabled button, .staticman-comments .page__comments-form.disabled textarea, .staticman-comments .page__comments-form.disabled label {
+  pointer-events: none;
+  cursor: not-allowed;
+  filter: alpha(opacity=65);
+  box-shadow: none;
+  opacity: 0.65;
+}
+.staticman-comments .comment {
+  margin: 1em 0;
+}
+.staticman-comments .comment:not(:last-child) {
+  border-bottom: 1px solid #f2f3f3;
+}
+.staticman-comments .comment__avatar-wrapper {
+  float: left;
+  width: 60px;
+  height: 60px;
+}
+.staticman-comments .comment__avatar {
+  width: 40px;
+  height: 40px;
+  border-radius: 50%;
+}
+.staticman-comments .comment__content-wrapper {
+  width: calc(100% - 60px);
+}
+.staticman-comments .comment__author {
+  margin: 0;
+}
+.staticman-comments .comment__author a {
+  text-decoration: none;
+}
+.staticman-comments .comment__date {
+  margin: 0;
+}
+.staticman-comments .comment__date a {
+  text-decoration: none;
+}
+/* ==========================================================================
+ PRINT STYLES
+ ========================================================================== */
+.staticman-comments @media print {
+  /*
+   Hide the following elements on print
+   ========================================================================== */
+.staticman-comments [hidden] {
+    display: none;
+  }
+.staticman-comments .masthead, .staticman-comments .toc, .staticman-comments .page__share, .staticman-comments .page__related, .staticman-comments .pagination, .staticman-comments .ads, .staticman-comments .page__footer, .staticman-comments .page__comments-form, .staticman-comments .author__avatar, .staticman-comments .author__content, .staticman-comments .author__urls-wrapper, .staticman-comments .nav__list, .staticman-comments .sidebar, .staticman-comments .adsbygoogle {
+    display: none !important;
+    height: 1px !important;
+  }
+}
+/*
+ Post pagination navigation links
+ ========================================================================== */
+.staticman-comments .page__comments + .staticman-comments .pagination {
+  margin-top: 2em;
+  padding-top: 2em;
+  border-top: 1px solid #f2f3f3;
+}

blog.bryanroessler.com/feed.xml

@@ -6,8 +6,8 @@ layout: null
   <channel>
     <title>{{ site.title | xml_escape }}</title>
     <description>{{ site.description | xml_escape }}</description>
-    <link>{{ site.url }}</link>
-    <atom:link href="{{ site.url }}/feed.xml" rel="self" type="application/rss+xml" />
+    <link>{{ '' | absolute_url }}</link>
+    <atom:link href="{{ 'feed.xml' | absolute_url }}" rel="self" type="application/rss+xml" />
     {% for post in site.posts limit:20 %}
       <item>
         <title>{{ post.title | xml_escape }}</title>
@@ -16,8 +16,8 @@ layout: null
           {{ post.content | strip_html | xml_escape | truncatewords: 50 }}
         </description>
         <pubDate>{{ post.date | date: "%a, %d %b %Y %H:%M:%S %z" }}</pubDate>
-        <link>{{ site.url }}{{ post.url }}</link>
-        <guid isPermaLink="true">{{ site.url }}{{ post.url }}</guid>
+        <link>{{ post.url | absolute_url }}</link>
+        <guid isPermaLink="true">{{ post.url | absolute_url }}</guid>
       </item>
     {% endfor %}
   </channel>

blog.bryanroessler.com/index.html

@@ -1,14 +1,14 @@
 ---
-layout: page
-<!--title: My website
-subtitle: This is where I will tell my friends way too much about me-->
+layout: home
+title: 
+subtitle: Bryan Roessler's Blog
 use-site-title: false
 ---
 
 <div class="posts-list">
   {% for post in paginator.posts %}
   <article class="post-preview">
-    <a href="{{ post.url | prepend: site.baseurl }}">
+    <a href="{{ post.url | relative_url }}">
 	  <h2 class="post-title">{{ post.title }}</h2>
 
 	  {% if post.subtitle %}
@@ -19,14 +19,14 @@ use-site-title: false
     </a>
 
     <p class="post-meta">
-      Posted on {{ post.date | date: "%B %-d, %Y" }}
+      Posted on {{ post.date | date: site.date_format }}
     </p>
 
     <div class="post-entry-container">
       {% if post.image %}
       <div class="post-image">
-        <a href="{{ post.url | prepend: site.baseurl }}">
-          <img src="{{ post.image }}">
+        <a href="{{ post.url | relative_url }}">
+          <img src="{{ post.image | relative_url }}">
         </a>
       </div>
       {% endif %}
@@ -34,7 +34,7 @@ use-site-title: false
         {{ post.excerpt | strip_html | xml_escape | truncatewords: site.excerpt_length }}
         {% assign excerpt_word_count = post.excerpt | number_of_words %}
         {% if post.content != post.excerpt or excerpt_word_count > site.excerpt_length %}
-          <a href="{{ post.url | prepend: site.baseurl }}" class="post-read-more">[Read&nbsp;More]</a>
+          <a href="{{ post.url | relative_url }}" class="post-read-more">[Read&nbsp;More]</a>
         {% endif %}
       </div>
     </div>
@@ -44,7 +44,7 @@ use-site-title: false
       Tags:
       {% if site.link-tags %}
       {% for tag in post.tags %}
-      <a href="{{ site.baseurl }}/tags#{{- tag -}}">{{- tag -}}</a>
+      <a href="{{ '/tags' | relative_url }}#{{- tag -}}">{{- tag -}}</a>
       {% endfor %}
       {% else %}
         {{ post.tags | join: ", " }}
@@ -60,12 +60,12 @@ use-site-title: false
 <ul class="pager main-pager">
   {% if paginator.previous_page %}
   <li class="previous">
-    <a href="{{ paginator.previous_page_path | prepend: site.baseurl | replace: '//', '/' }}">&larr; Newer Posts</a>
+    <a href="{{ paginator.previous_page_path | relative_url }}">&larr; Newer Posts</a>
   </li>
   {% endif %}
   {% if paginator.next_page %}
   <li class="next">
-    <a href="{{ paginator.next_page_path | prepend: site.baseurl | replace: '//', '/' }}">Older Posts &rarr;</a>
+    <a href="{{ paginator.next_page_path | relative_url }}">Older Posts &rarr;</a>
   </li>
   {% endif %}
 </ul>

blog.bryanroessler.com/js/staticman.js

@@ -0,0 +1,54 @@
+---
+layout: null
+---
+
+(function ($) {
+  var $comments = $('.js-comments');
+
+  $('#new_comment').submit(function () {
+    var form = this;
+
+    $(form).addClass('disabled');
+
+    {% assign sm = site.staticman -%}
+    var endpoint = '{{ sm.endpoint | default: "https://staticman3.herokuapp.com/v3/entry/github/" }}';
+    var repository = '{{ sm.repository }}';
+    var branch = '{{ sm.branch }}';
+
+    $.ajax({
+      type: $(this).attr('method'),
+      url: endpoint + repository + '/' + branch + '/comments',
+      data: $(this).serialize(),
+      contentType: 'application/x-www-form-urlencoded',
+      success: function (data) {
+        $('#comment-form-submit').addClass('hidden');
+        $('#comment-form-submitted').removeClass('hidden');
+        $('.page__comments-form .js-notice').removeClass('notice--danger');
+        $('.page__comments-form .js-notice').addClass('notice--success');
+        showAlert('success');
+      },
+      error: function (err) {
+        console.log(err);
+        $('#comment-form-submitted').addClass('hidden');
+        $('#comment-form-submit').removeClass('hidden');
+        $('.page__comments-form .js-notice').removeClass('notice--success');
+        $('.page__comments-form .js-notice').addClass('notice--danger');
+        showAlert('failure');
+        $(form).removeClass('disabled');
+      }
+    });
+
+    return false;
+  });
+
+  function showAlert(message) {
+    $('.page__comments-form .js-notice').removeClass('hidden');
+    if (message == 'success') {
+      $('.page__comments-form .js-notice-text-success').removeClass('hidden');
+      $('.page__comments-form .js-notice-text-failure').addClass('hidden');
+    } else {
+      $('.page__comments-form .js-notice-text-success').addClass('hidden');
+      $('.page__comments-form .js-notice-text-failure').removeClass('hidden');
+    }
+  }
+})(jQuery);

blog.bryanroessler.com/staticman.yml

@@ -0,0 +1,110 @@
+# Name of the property. You can have multiple properties with completely
+# different config blocks for different sections of your site.
+# For example, you can have one property to handle comment submission and
+# another one to handle posts.
+# To encrypt strings use the following endpoint:
+# https://{STATICMAN API INSTANCE}/v3/encrypt/{TEXT TO BE ENCRYPTED}
+# {STATICMAN API INSTANCE} should match the `endpoint` in the theme config
+# file. It defaults to "staticman3.herokuapp.com".
+
+comments:
+  # (*) REQUIRED
+  #
+  # Names of the fields the form is allowed to submit. If a field that is
+  # not here is part of the request, an error will be thrown.
+  allowedFields: ["name", "email", "url", "message"]
+
+  # (*) REQUIRED WHEN USING NOTIFICATIONS
+  #
+  # When allowedOrigins is defined, only requests sent from one of the domains
+  # listed will be accepted. The origin is sent as part as the `options` object
+  # (e.g. <input name="options[origin]" value="http://yourdomain.com/post1")
+  # allowedOrigins: ["https://example.com"]
+
+  # (*) REQUIRED
+  #
+  # Name of the branch being used. Must match the `branch` in the theme config
+  # file.
+  branch: "master"   #  use "master" for user page or "gh-pages" for project pages
+
+  commitMessage: "New comment by {fields.name}"
+
+  # (*) REQUIRED
+  #
+  # Destination path (filename) for the data files. Accepts placeholders.
+  filename: "comment-{@timestamp}"
+
+  # The format of the generated data files. Accepted values are "json", "yaml"
+  # or "frontmatter"
+  format: "yaml"
+
+  # List of fields to be populated automatically by Staticman and included in
+  # the data file. Keys are the name of the field. The value can be an object
+  # with a `type` property, which configures the generated field, or any value
+  # to be used directly (e.g. a string, number or array)
+  generatedFields:
+    date:
+      type: "date"
+      options:
+        format: "iso8601" # "iso8601" (default), "timestamp-seconds", "timestamp-milliseconds"
+
+  # Whether entries need to be approved before they are published to the main
+  # branch. If set to `true`, a pull request will be created for your approval.
+  # Otherwise, entries will be published to the main branch automatically.
+  moderation: false
+
+  # Akismet spam detection.
+  # akismet:
+  #   enabled: true
+  #   author: "name"
+  #   authorEmail: "email"
+  #   authorUrl: "url"
+  #   content: "message"
+  #   type: "comment"
+
+  # Name of the site. Used in notification emails.
+  # name: "Your Site"
+
+  # Notification settings. When enabled, users can choose to receive notifications
+  # via email when someone adds a reply or a new comment. This requires an account
+  # with Mailgun, which you can get for free at http://mailgun.com.
+  # notifications:
+    # Enable notifications
+    # enabled: true
+
+    # (!) ENCRYPTED
+    #
+    # Mailgun API key
+    # apiKey: ""
+
+    # (!) ENCRYPTED
+    #
+    # Mailgun domain (encrypted)
+    # domain: ""
+
+  # (*) REQUIRED
+  #
+  # Destination path (directory) for the data files. Accepts placeholders.
+  path: "_data/comments/{options.slug}" # (default)
+
+  # Names of required files. If any of these isn't in the request or is empty,
+  # an error will be thrown.
+  requiredFields: ["name", "email", "message"]
+
+  # List of transformations to apply to any of the fields supplied. Keys are
+  # the name of the field and values are possible transformation types.
+  transforms:
+    email: md5
+
+  # reCAPTCHA (OPTIONAL)
+  # To enable reCAPTCHA:
+  # 1. Set `enabled` to `true`
+  # 2. Register your domain at https://www.google.com/recaptcha/ and choose reCAPTCHA V2
+  # 3. Uncomment `siteKey` and `secret` and fill them in with your values
+  reCaptcha:
+    enabled: false
+    #siteKey: ""
+    # ENCRYPT reCaptcha secret key using Staticman /encrypt endpoint
+    # i.e. https://{STATICMAN API INSTANCE}/v3/encrypt/{your-site-secret}
+    # For more information, visit https://staticman.net/docs/encryption
+    #secret: ""

blog.bryanroessler.com/tags.html

@@ -3,6 +3,8 @@ layout: page
 title: 'Tag Index'
 ---
 
+{% assign date_format = site.date_format | default: "%B %-d, %Y" %}
+
 {%- capture site_tags -%}
     {%- for tag in site.tags -%}
         {{- tag | first -}}{%- unless forloop.last -%},{%- endunless -%}
@@ -11,21 +13,21 @@ title: 'Tag Index'
 {%- assign tags_list = site_tags | split:',' | sort -%}
 
 {%- for tag in tags_list -%}
-    <a href="#{{- tag -}}" class="btn btn-primary tag-btn"><i class="fa fa-tag" aria-hidden="true"></i>&nbsp;{{- tag -}}&nbsp;({{site.tags[tag].size}})</a>
+    <a href="#{{- tag -}}" class="btn btn-primary tag-btn"><i class="fas fa-tag" aria-hidden="true"></i>&nbsp;{{- tag -}}&nbsp;({{site.tags[tag].size}})</a>
 {%- endfor -%}
 
 <div id="full-tags-list">
 {%- for tag in tags_list -%}
     <h2 id="{{- tag -}}" class="linked-section">
-        <i class="fa fa-tag" aria-hidden="true"></i>
+        <i class="fas fa-tag" aria-hidden="true"></i>
         &nbsp;{{- tag -}}&nbsp;({{site.tags[tag].size}})
     </h2>
     <div class="post-list">
         {%- for post in site.tags[tag] -%}
             <div class="tag-entry">
-                <a href="{{- site.url -}}{{- post.url -}}">{{- post.title -}}</a>
+                <a href="{{ post.url | relative_url }}">{{- post.title | strip_html -}}</a>
                 <div class="entry-date">
-                    <time datetime="{{- post.date | date_to_xmlschema -}}">{{- post.date | date: "%B %d, %Y" -}}</time>
+                    <time datetime="{{- post.date | date_to_xmlschema -}}">{{- post.date | date: date_format -}}</time>
                 </div>
             </div>
         {%- endfor -%}

build.sh

@@ -0,0 +1,22 @@
+#!/usr/bin/env bash
+
+# build and deploy
+#podman build \
+#    --rm \
+#    -it \
+#    -v "$PWD:/srv/jekyll" \
+#    -v "$PWD/vendor/bundle:/usr/local/bundle" \
+#    -u 1000:1001 \
+#    jekyll:latest \
+#    bundle update
+
+podman build -t atomjekylltemp .
+podman run \
+    --rm \
+    -it \
+    -p 4000:4000 \
+    -v "$PWD:/srv/jekyll" \
+    -v "$PWD/vendor/bundle:/usr/local/bundle" \
+    localhost/atomjekylltemp
+
+#podman rmi localhost/atomjekylltemp

cv.bryanroessler.com/.dockerignore

@@ -0,0 +1,7 @@
+.git
+.git/
+.gitignore
+_site
+.sass-cache
+.DS_Store
+_vendor

cv.bryanroessler.com/Dockerfile

@@ -0,0 +1,11 @@
+FROM ruby:2.7
+
+WORKDIR /home/app
+
+COPY Gemfile* ./
+
+RUN bundle install
+
+COPY . .
+
+CMD [ "bundle", "exec", "jekyll", "serve" ]

cv.bryanroessler.com/Gemfile

@@ -2,3 +2,5 @@ source "https://rubygems.org"
 
 gem 'github-pages'
 gem 'rake'
+gem 'webrick'
+

cv.bryanroessler.com/Gemfile.lock

@@ -1,250 +1,314 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (4.2.10)
-      i18n (~> 0.7)
-      minitest (~> 5.1)
-      thread_safe (~> 0.3, >= 0.3.4)
-      tzinfo (~> 1.1)
-    addressable (2.5.2)
-      public_suffix (>= 2.0.2, < 4.0)
+    activesupport (8.0.0)
+      base64
+      benchmark (>= 0.3)
+      bigdecimal
+      concurrent-ruby (~> 1.0, >= 1.3.1)
+      connection_pool (>= 2.2.5)
+      drb
+      i18n (>= 1.6, < 2)
+      logger (>= 1.4.2)
+      minitest (>= 5.1)
+      securerandom (>= 0.3)
+      tzinfo (~> 2.0, >= 2.0.5)
+      uri (>= 0.13.1)
+    addressable (2.8.7)
+      public_suffix (>= 2.0.2, < 7.0)
+    base64 (0.2.0)
+    benchmark (0.4.0)
+    bigdecimal (3.1.8)
     coffee-script (2.4.1)
       coffee-script-source
       execjs
-    coffee-script-source (1.11.1)
+    coffee-script-source (1.12.2)
     colorator (1.1.0)
-    commonmarker (0.17.13)
-      ruby-enum (~> 0.5)
-    concurrent-ruby (1.1.3)
-    dnsruby (1.61.2)
-      addressable (~> 2.5)
-    em-websocket (0.5.1)
+    commonmarker (0.23.11)
+    concurrent-ruby (1.3.4)
+    connection_pool (2.4.1)
+    csv (3.3.0)
+    dnsruby (1.72.3)
+      base64 (~> 0.2.0)
+      simpleidn (~> 0.2.1)
+    drb (2.2.1)
+    em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
-      http_parser.rb (~> 0.6.0)
-    ethon (0.11.0)
-      ffi (>= 1.3.0)
+      http_parser.rb (~> 0)
+    ethon (0.16.0)
+      ffi (>= 1.15.0)
     eventmachine (1.2.7)
-    execjs (2.7.0)
-    faraday (0.15.4)
-      multipart-post (>= 1.2, < 3)
-    ffi (1.9.25)
+    execjs (2.10.0)
+    faraday (2.12.1)
+      faraday-net_http (>= 2.0, < 3.5)
+      json
+      logger
+    faraday-net_http (3.4.0)
+      net-http (>= 0.5.0)
+    ffi (1.17.0-aarch64-linux-gnu)
+    ffi (1.17.0-aarch64-linux-musl)
+    ffi (1.17.0-arm-linux-gnu)
+    ffi (1.17.0-arm-linux-musl)
+    ffi (1.17.0-arm64-darwin)
+    ffi (1.17.0-x86-linux-gnu)
+    ffi (1.17.0-x86-linux-musl)
+    ffi (1.17.0-x86_64-darwin)
+    ffi (1.17.0-x86_64-linux-gnu)
+    ffi (1.17.0-x86_64-linux-musl)
     forwardable-extended (2.6.0)
-    gemoji (3.0.0)
-    github-pages (193)
-      activesupport (= 4.2.10)
-      github-pages-health-check (= 1.8.1)
-      jekyll (= 3.7.4)
-      jekyll-avatar (= 0.6.0)
-      jekyll-coffeescript (= 1.1.1)
-      jekyll-commonmark-ghpages (= 0.1.5)
-      jekyll-default-layout (= 0.1.4)
-      jekyll-feed (= 0.11.0)
+    gemoji (4.1.0)
+    github-pages (232)
+      github-pages-health-check (= 1.18.2)
+      jekyll (= 3.10.0)
+      jekyll-avatar (= 0.8.0)
+      jekyll-coffeescript (= 1.2.2)
+      jekyll-commonmark-ghpages (= 0.5.1)
+      jekyll-default-layout (= 0.1.5)
+      jekyll-feed (= 0.17.0)
       jekyll-gist (= 1.5.0)
-      jekyll-github-metadata (= 2.9.4)
-      jekyll-mentions (= 1.4.1)
-      jekyll-optional-front-matter (= 0.3.0)
+      jekyll-github-metadata (= 2.16.1)
+      jekyll-include-cache (= 0.2.1)
+      jekyll-mentions (= 1.6.0)
+      jekyll-optional-front-matter (= 0.3.2)
       jekyll-paginate (= 1.1.0)
-      jekyll-readme-index (= 0.2.0)
-      jekyll-redirect-from (= 0.14.0)
-      jekyll-relative-links (= 0.5.3)
-      jekyll-remote-theme (= 0.3.1)
+      jekyll-readme-index (= 0.3.0)
+      jekyll-redirect-from (= 0.16.0)
+      jekyll-relative-links (= 0.6.1)
+      jekyll-remote-theme (= 0.4.3)
       jekyll-sass-converter (= 1.5.2)
-      jekyll-seo-tag (= 2.5.0)
-      jekyll-sitemap (= 1.2.0)
-      jekyll-swiss (= 0.4.0)
-      jekyll-theme-architect (= 0.1.1)
-      jekyll-theme-cayman (= 0.1.1)
-      jekyll-theme-dinky (= 0.1.1)
-      jekyll-theme-hacker (= 0.1.1)
-      jekyll-theme-leap-day (= 0.1.1)
-      jekyll-theme-merlot (= 0.1.1)
-      jekyll-theme-midnight (= 0.1.1)
-      jekyll-theme-minimal (= 0.1.1)
-      jekyll-theme-modernist (= 0.1.1)
-      jekyll-theme-primer (= 0.5.3)
-      jekyll-theme-slate (= 0.1.1)
-      jekyll-theme-tactile (= 0.1.1)
-      jekyll-theme-time-machine (= 0.1.1)
-      jekyll-titles-from-headings (= 0.5.1)
-      jemoji (= 0.10.1)
-      kramdown (= 1.17.0)
-      liquid (= 4.0.0)
-      listen (= 3.1.5)
+      jekyll-seo-tag (= 2.8.0)
+      jekyll-sitemap (= 1.4.0)
+      jekyll-swiss (= 1.0.0)
+      jekyll-theme-architect (= 0.2.0)
+      jekyll-theme-cayman (= 0.2.0)
+      jekyll-theme-dinky (= 0.2.0)
+      jekyll-theme-hacker (= 0.2.0)
+      jekyll-theme-leap-day (= 0.2.0)
+      jekyll-theme-merlot (= 0.2.0)
+      jekyll-theme-midnight (= 0.2.0)
+      jekyll-theme-minimal (= 0.2.0)
+      jekyll-theme-modernist (= 0.2.0)
+      jekyll-theme-primer (= 0.6.0)
+      jekyll-theme-slate (= 0.2.0)
+      jekyll-theme-tactile (= 0.2.0)
+      jekyll-theme-time-machine (= 0.2.0)
+      jekyll-titles-from-headings (= 0.5.3)
+      jemoji (= 0.13.0)
+      kramdown (= 2.4.0)
+      kramdown-parser-gfm (= 1.1.0)
+      liquid (= 4.0.4)
       mercenary (~> 0.3)
-      minima (= 2.5.0)
-      nokogiri (>= 1.8.2, < 2.0)
-      rouge (= 2.2.1)
+      minima (= 2.5.1)
+      nokogiri (>= 1.16.2, < 2.0)
+      rouge (= 3.30.0)
       terminal-table (~> 1.4)
-    github-pages-health-check (1.8.1)
+      webrick (~> 1.8)
+    github-pages-health-check (1.18.2)
       addressable (~> 2.3)
       dnsruby (~> 1.60)
-      octokit (~> 4.0)
-      public_suffix (~> 2.0)
+      octokit (>= 4, < 8)
+      public_suffix (>= 3.0, < 6.0)
       typhoeus (~> 1.3)
-    html-pipeline (2.9.1)
+    html-pipeline (2.14.3)
       activesupport (>= 2)
       nokogiri (>= 1.4)
-    http_parser.rb (0.6.0)
-    i18n (0.9.5)
+    http_parser.rb (0.8.0)
+    i18n (1.14.6)
       concurrent-ruby (~> 1.0)
-    jekyll (3.7.4)
+    jekyll (3.10.0)
       addressable (~> 2.4)
       colorator (~> 1.0)
+      csv (~> 3.0)
       em-websocket (~> 0.5)
-      i18n (~> 0.7)
+      i18n (>= 0.7, < 2)
       jekyll-sass-converter (~> 1.0)
       jekyll-watch (~> 2.0)
-      kramdown (~> 1.14)
+      kramdown (>= 1.17, < 3)
       liquid (~> 4.0)
       mercenary (~> 0.3.3)
       pathutil (~> 0.9)
       rouge (>= 1.7, < 4)
       safe_yaml (~> 1.0)
-    jekyll-avatar (0.6.0)
-      jekyll (~> 3.0)
-    jekyll-coffeescript (1.1.1)
+      webrick (>= 1.0)
+    jekyll-avatar (0.8.0)
+      jekyll (>= 3.0, < 5.0)
+    jekyll-coffeescript (1.2.2)
       coffee-script (~> 2.2)
-      coffee-script-source (~> 1.11.1)
-    jekyll-commonmark (1.2.0)
-      commonmarker (~> 0.14)
-      jekyll (>= 3.0, < 4.0)
-    jekyll-commonmark-ghpages (0.1.5)
-      commonmarker (~> 0.17.6)
-      jekyll-commonmark (~> 1)
-      rouge (~> 2)
-    jekyll-default-layout (0.1.4)
-      jekyll (~> 3.0)
-    jekyll-feed (0.11.0)
-      jekyll (~> 3.3)
+      coffee-script-source (~> 1.12)
+    jekyll-commonmark (1.4.0)
+      commonmarker (~> 0.22)
+    jekyll-commonmark-ghpages (0.5.1)
+      commonmarker (>= 0.23.7, < 1.1.0)
+      jekyll (>= 3.9, < 4.0)
+      jekyll-commonmark (~> 1.4.0)
+      rouge (>= 2.0, < 5.0)
+    jekyll-default-layout (0.1.5)
+      jekyll (>= 3.0, < 5.0)
+    jekyll-feed (0.17.0)
+      jekyll (>= 3.7, < 5.0)
     jekyll-gist (1.5.0)
       octokit (~> 4.2)
-    jekyll-github-metadata (2.9.4)
-      jekyll (~> 3.1)
-      octokit (~> 4.0, != 4.4.0)
-    jekyll-mentions (1.4.1)
+    jekyll-github-metadata (2.16.1)
+      jekyll (>= 3.4, < 5.0)
+      octokit (>= 4, < 7, != 4.4.0)
+    jekyll-include-cache (0.2.1)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-mentions (1.6.0)
       html-pipeline (~> 2.3)
-      jekyll (~> 3.0)
-    jekyll-optional-front-matter (0.3.0)
-      jekyll (~> 3.0)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-optional-front-matter (0.3.2)
+      jekyll (>= 3.0, < 5.0)
     jekyll-paginate (1.1.0)
-    jekyll-readme-index (0.2.0)
-      jekyll (~> 3.0)
-    jekyll-redirect-from (0.14.0)
-      jekyll (~> 3.3)
-    jekyll-relative-links (0.5.3)
-      jekyll (~> 3.3)
-    jekyll-remote-theme (0.3.1)
-      jekyll (~> 3.5)
-      rubyzip (>= 1.2.1, < 3.0)
+    jekyll-readme-index (0.3.0)
+      jekyll (>= 3.0, < 5.0)
+    jekyll-redirect-from (0.16.0)
+      jekyll (>= 3.3, < 5.0)
+    jekyll-relative-links (0.6.1)
+      jekyll (>= 3.3, < 5.0)
+    jekyll-remote-theme (0.4.3)
+      addressable (~> 2.0)
+      jekyll (>= 3.5, < 5.0)
+      jekyll-sass-converter (>= 1.0, <= 3.0.0, != 2.0.0)
+      rubyzip (>= 1.3.0, < 3.0)
     jekyll-sass-converter (1.5.2)
       sass (~> 3.4)
-    jekyll-seo-tag (2.5.0)
-      jekyll (~> 3.3)
-    jekyll-sitemap (1.2.0)
-      jekyll (~> 3.3)
-    jekyll-swiss (0.4.0)
-    jekyll-theme-architect (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-seo-tag (2.8.0)
+      jekyll (>= 3.8, < 5.0)
+    jekyll-sitemap (1.4.0)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-swiss (1.0.0)
+    jekyll-theme-architect (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-cayman (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-cayman (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-dinky (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-dinky (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-hacker (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-hacker (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-leap-day (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-leap-day (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-merlot (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-merlot (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-midnight (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-midnight (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-minimal (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-minimal (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-modernist (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-modernist (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-primer (0.5.3)
-      jekyll (~> 3.5)
+    jekyll-theme-primer (0.6.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-github-metadata (~> 2.9)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-slate (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-slate (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-tactile (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-tactile (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-time-machine (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-time-machine (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-titles-from-headings (0.5.1)
-      jekyll (~> 3.3)
-    jekyll-watch (2.1.2)
+    jekyll-titles-from-headings (0.5.3)
+      jekyll (>= 3.3, < 5.0)
+    jekyll-watch (2.2.1)
       listen (~> 3.0)
-    jemoji (0.10.1)
-      gemoji (~> 3.0)
+    jemoji (0.13.0)
+      gemoji (>= 3, < 5)
       html-pipeline (~> 2.2)
-      jekyll (~> 3.0)
-    kramdown (1.17.0)
-    liquid (4.0.0)
-    listen (3.1.5)
-      rb-fsevent (~> 0.9, >= 0.9.4)
-      rb-inotify (~> 0.9, >= 0.9.7)
-      ruby_dep (~> 1.2)
+      jekyll (>= 3.0, < 5.0)
+    json (2.9.0)
+    kramdown (2.4.0)
+      rexml
+    kramdown-parser-gfm (1.1.0)
+      kramdown (~> 2.0)
+    liquid (4.0.4)
+    listen (3.9.0)
+      rb-fsevent (~> 0.10, >= 0.10.3)
+      rb-inotify (~> 0.9, >= 0.9.10)
+    logger (1.6.2)
     mercenary (0.3.6)
-    mini_portile2 (2.3.0)
-    minima (2.5.0)
-      jekyll (~> 3.5)
+    minima (2.5.1)
+      jekyll (>= 3.5, < 5.0)
       jekyll-feed (~> 0.9)
       jekyll-seo-tag (~> 2.1)
-    minitest (5.11.3)
-    multipart-post (2.0.0)
-    nokogiri (1.8.5)
-      mini_portile2 (~> 2.3.0)
-    octokit (4.13.0)
-      sawyer (~> 0.8.0, >= 0.5.3)
+    minitest (5.25.4)
+    net-http (0.6.0)
+      uri
+    nokogiri (1.16.8-aarch64-linux)
+      racc (~> 1.4)
+    nokogiri (1.16.8-arm-linux)
+      racc (~> 1.4)
+    nokogiri (1.16.8-arm64-darwin)
+      racc (~> 1.4)
+    nokogiri (1.16.8-x86-linux)
+      racc (~> 1.4)
+    nokogiri (1.16.8-x86_64-darwin)
+      racc (~> 1.4)
+    nokogiri (1.16.8-x86_64-linux)
+      racc (~> 1.4)
+    octokit (4.25.1)
+      faraday (>= 1, < 3)
+      sawyer (~> 0.9)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    public_suffix (2.0.5)
-    rake (12.3.1)
-    rb-fsevent (0.10.3)
-    rb-inotify (0.9.10)
-      ffi (>= 0.5.0, < 2)
-    rouge (2.2.1)
-    ruby-enum (0.7.2)
-      i18n
-    ruby_dep (1.5.0)
-    rubyzip (1.2.2)
-    safe_yaml (1.0.4)
-    sass (3.7.2)
+    public_suffix (5.1.1)
+    racc (1.8.1)
+    rake (13.2.1)
+    rb-fsevent (0.11.2)
+    rb-inotify (0.11.1)
+      ffi (~> 1.0)
+    rexml (3.3.9)
+    rouge (3.30.0)
+    rubyzip (2.3.2)
+    safe_yaml (1.0.5)
+    sass (3.7.4)
       sass-listen (~> 4.0.0)
     sass-listen (4.0.0)
       rb-fsevent (~> 0.9, >= 0.9.4)
       rb-inotify (~> 0.9, >= 0.9.7)
-    sawyer (0.8.1)
-      addressable (>= 2.3.5, < 2.6)
-      faraday (~> 0.8, < 1.0)
+    sawyer (0.9.2)
+      addressable (>= 2.3.5)
+      faraday (>= 0.17.3, < 3)
+    securerandom (0.4.0)
+    simpleidn (0.2.3)
     terminal-table (1.8.0)
       unicode-display_width (~> 1.1, >= 1.1.1)
-    thread_safe (0.3.6)
-    typhoeus (1.3.1)
+    typhoeus (1.4.1)
       ethon (>= 0.9.0)
-    tzinfo (1.2.5)
-      thread_safe (~> 0.1)
-    unicode-display_width (1.4.0)
+    tzinfo (2.0.6)
+      concurrent-ruby (~> 1.0)
+    unicode-display_width (1.8.0)
+    uri (1.0.2)
+    webrick (1.9.1)
 
 PLATFORMS
-  ruby
+  aarch64-linux
+  aarch64-linux-gnu
+  aarch64-linux-musl
+  arm-linux
+  arm-linux-gnu
+  arm-linux-musl
+  arm64-darwin
+  x86-linux
+  x86-linux-gnu
+  x86-linux-musl
+  x86_64-darwin
+  x86_64-linux-gnu
+  x86_64-linux-musl
 
 DEPENDENCIES
   github-pages
   rake
+  webrick
 
 BUNDLED WITH
-   1.16.2
+   2.5.22

cv.bryanroessler.com/README.md

@@ -15,6 +15,13 @@ To test locally, run the following in your terminal:
 2. `bundle exec jekyll serve`
 3. Open your browser to `localhost:4000`
 
+### Running locally with Docker
+
+To test locally with docker, run the following in your terminal after installing docker into your system:
+
+1. `docker image build -t resume-template .`
+2. `docker run --rm --name resume-template -v "$PWD":/home/app --network host resume-template`
+
 ### Customizing
 
 First you'll want to fork the repo to your own account. Then clone it locally and customize, or use the GitHub web editor to customize.
@@ -56,4 +63,4 @@ If you spot a bug, or want to improve the code, or even make the dummy content b
 
 The code and styles are licensed under the MIT license. [See project license.](LICENSE) Obviously you should not use the content of this demo repo in your own resume. :wink:
 
-Disclaimer: Use of Homer J. Simpson image and name used under [Fair Use](https://en.wikipedia.org/wiki/Fair_use) for educational purposes. Project license does not apply to use of this material.
+Disclaimer: Use of Lisa M. Simpson image and name used under [Fair Use](https://en.wikipedia.org/wiki/Fair_use) for educational purposes. Project license does not apply to use of this material.

cv.bryanroessler.com/_config.yml

@@ -12,7 +12,7 @@ sass:
 # Resume settings
 resume_avatar:                  "true"
 resume_name:                    "Bryan C. Roessler"
-resume_title:                   "Research Assistant"
+resume_title:                   "Software Developer"
 
 # used for the contact button in _layouts/resume.html
 resume_contact_email:           "bryanroessler@gmail.com"
@@ -25,10 +25,9 @@ resume_header_contact_info:     "St. Petersburg, FL • bryanroessler@gmail.com"
 display_header_contact_info:    "true"
 
 resume_header_intro: >
-                    <p>I am a computational biologist specializing in molecular
-                    dynamics that is currently seeking a creative and impactful
-                    position in the academic, pharmaceutical, or biotechnology
-                    sectors.</p>
+                    <p>I am a full-stack software developer with a background in high-performance computing and molecular dynamics.
+                    I excel at breaking complex problems into simple, solvable solutions. In my free time I enjoy contributing
+                    to a variety of open source projects within the Linux ecosystem.</p>
 
 # use "yes" to display the email contact button,
 # "no" to display an "I'm not looking for work" message,

cv.bryanroessler.com/_data/experience.yml

@@ -1,23 +1,12 @@
 # Jobs
-- company: University of Alabama at Birmingham
-  position: Research Assistant
+- company: BRSoftware
+  position: Lead Software Developer and Consultant
   duration: Jan 2018 — Present
   summary: >
-    I'm currently completing work on two projects: <ul class="resume-item-list">
-    <li>Modifed substrate effects on the binding mechanisms of Sortase A, a
-    revised model. <i>In review.</i></li>
-    <li>The role of constitutive gain-of-function mutations on the structure and dynamics of the cystic fibrosis transmembrane conductance regulator.</li>
+    I create full-stack software solutions for clients in a variety of programming languages.
 
 - company: University of Alabama at Birmingham
   position: Graduate Research Assistant
-  duration:  Aug 2010 &mdash; Dec 2017
+  duration:  Aug 2010 &mdash; Jan 2018
   summary: >
-    My doctoral thesis focused on the use of computational molecular dynamics to understand the impact of mutations and empirical structural determination methods on the
-    function and dynamics of multidrug resistance (specifically, CFTR) and sortase proteins.
-
-- company: U.S. Census Bureau
-  position: Crew Leader
-  duration: Jan 2010  &mdash; May 2010
-  summary: >
-    Supervised a team of enumerators to ensure assigned tasks were completed properly.
-    Monitored and evaluated performance for adjustments and improvements.
+    My doctoral thesis utilized computational molecular dynamics to study the effects of mutations on the structure and function of multidrug resistance proteins.

cv.bryanroessler.com/_data/interests.yml

@@ -1,8 +1,3 @@
-# Interests
-- description: Futurology, Automation & AI
-- description: Open-source Software
-- description: Computer Hardware
-- description: Fitness & Nutrition
-- description: E-Bikes
-- description: Pet Fostering
-- description: College Basketball (Go Zags!)
+
+
+