chore: addition of things

Author: lholmquist

.github/workflows/github-pages.yml

@@ -0,0 +1,15 @@
+name: Build and deploy Jekyll site to GitHub Pages
+
+on:
+  push:
+    branches:
+      - f-in-around-new-site
+
+jobs:
+  github-pages:
+    runs-on: ubuntu-16.04
+    steps:
+      - uses: actions/checkout@v2
+      - uses: helaili/[email protected]
+        env:
+          JEKYLL_PAT: ${{ secrets.JEKYLL_PAT }}

Gemfile

@@ -20,7 +20,9 @@ gem "minima", "~> 2.0"
 # If you have any plugins, put them here!
 group :jekyll_plugins do
   gem "jekyll-feed", "~> 0.6"
+  gem 'jekyll-asciidoc'
   gem 'jekyll-paginate-v2'
+  gem 'jekyll-archives'
 end
 
 # Windows does not include zoneinfo files, so bundle the tzinfo-data gem

Gemfile.lock

@@ -3,8 +3,9 @@ GEM
   specs:
     addressable (2.7.0)
       public_suffix (>= 2.0.2, < 5.0)
+    asciidoctor (2.0.10)
     colorator (1.1.0)
-    concurrent-ruby (1.1.6)
+    concurrent-ruby (1.1.7)
     em-websocket (0.5.1)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0.6.0)
@@ -27,6 +28,11 @@ GEM
       pathutil (~> 0.9)
       rouge (>= 1.7, < 4)
       safe_yaml (~> 1.0)
+    jekyll-archives (2.2.1)
+      jekyll (>= 3.6, < 5.0)
+    jekyll-asciidoc (3.0.0)
+      asciidoctor (>= 1.5.0)
+      jekyll (>= 3.0.0)
     jekyll-feed (0.15.0)
       jekyll (>= 3.7, < 5.0)
     jekyll-paginate-v2 (3.0.0)
@@ -53,7 +59,7 @@ GEM
     rb-fsevent (0.10.4)
     rb-inotify (0.10.1)
       ffi (~> 1.0)
-    rouge (3.21.0)
+    rouge (3.22.0)
     safe_yaml (1.0.5)
     sass (3.7.4)
       sass-listen (~> 4.0.0)
@@ -66,10 +72,12 @@ PLATFORMS
 
 DEPENDENCIES
   jekyll (~> 3.8.3)
+  jekyll-archives
+  jekyll-asciidoc
   jekyll-feed (~> 0.6)
   jekyll-paginate-v2
   minima (~> 2.0)
   tzinfo-data
 
 BUNDLED WITH
-   1.17.2
+   2.1.4

_data/authors.yaml

@@ -1,6 +1,7 @@
 lholmquist:
   name: "Lucas Holmquist"
   email: "[email protected]"
+  emailhash: 4120ab1fe80040d03eb790c2efafadc9
   job_title: "Sr. Software Engineer"
   twitter: "sienaluke"
   bio: "Sr. Software Engineer at Red Hat.  Red Hat Runtimes Node.js Lead"

_includes/blog/blog-feed.html

@@ -3,7 +3,7 @@
     {% for post in paginator.posts %}
       {% assign author = site.data.authors[post.author] %}
       <div class="blog-list-item grid-wrapper">
-        <div class="post-date grid__item width-12-12">{{ post.date | date: '%B %d, %Y' }} 
+        <div class="post-date grid__item width-12-12">{{ post.date | date: '%B %d, %Y' }}
           {% for tag in post.tags %}<a href="{{site.baseurl}}/blog/tag/{{tag}}">#{{ tag}}</a> {% endfor %}
         </div>
         <div class="post-title grid__item width-12-12">
@@ -37,7 +37,7 @@
       </div>
       {% endif %}
   </div>
-  
+
   <div class="grid__item width-2-12">
     {% assign tag_words = site.tags | sort %}
     {% for stats in tag_words %}

_includes/blog/blog-titleband.html

@@ -9,4 +9,4 @@ <h1 class="title text-caps">{{ page.title }}</h1>
  				 </div>
 		</div>
 	</div>
-</div>
+</div>

_includes/site-header.html

@@ -4,6 +4,9 @@
   <meta charset="utf-8">
   <meta name="viewport" content="width=device-width">
   <meta name="description" content="{% if page.description %}{{ page.description }}{% else %}{{ site.description }}{% endif %}">
+  {% if page.cannonical_url %}
+    <link rel="cannonical" href="{{ page.cannonical_url }}">
+  {% endif %}
   <link rel="shortcut icon" type="image/png" href="{{ "/favicon.ico" | prepend: site.baseurl }}" >
   <link rel="stylesheet" href="{{ 'assets/css/main.css' | relative_url }}" />
   <link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.1.0/css/all.css" integrity="sha384-lKuwvrZot6UHsBSfcMvOkWwlCMgc0TaWr+30HWe3a4ltaBwTZhyTEggF5tJv8tbt" crossorigin="anonymous">

_posts/2018-04-16-zero-to-express.md

@@ -3,41 +3,48 @@ layout: post
 title:  "Zero to Express on OpenShift in Three Commands"
 date:   2018-04-16
 categories: Openshift Nodeshift
+cannonical_url: https://developers.redhat.com/blog/2018/04/16/zero-express-openshift-3-commands/
 author: lholmquist
 ---
 
-<strong>(Edit: November 22, 2019) The Node images used in this post, both community <code>centos7</code> and <code>product</code>, are no longer being updated and maintained. For community images, please use the Universal Base Image (UBI)-based node images located here: <a href="http://registry.access.redhat.com/ubi8/nodejs-10">registry.access.redhat.com/ubi8/nodejs-10</a></strong>
-
-<strong>For a fully supported Product version of Node.js, please check out the Red Hat Software Collections Node.js image, <a href="https://access.redhat.com/containers/#/registry.access.redhat.com/rhscl/nodejs-10-rhel7">RH SCL Node.js</a>.</strong>
-
 With the recent <a href="https://developers.redhat.com/blog/2018/03/12/rhoar-nodejs-annoucement/" target="_blank" rel="noopener noreferrer">announcement that Node.js is generally available as part of Red Hat OpenShift Application Runtimes,</a> I wanted to see how easy it was to deploy an <a href="https://expressjs.com/">Express.js</a> app on OpenShift.
 <h3>Getting Started</h3>
 Before we start, there are some required prerequisites. You need to have <a href="https://nodejs.org" target="_blank" rel="noopener noreferrer">Node 8.x</a> and <a href="https://www.npmjs.com/" target="_blank" rel="noopener noreferrer">npm 5.2 </a> or greater installed. npm comes with the official node distribution, so if you install Node from <a href="https://nodejs.org" target="_blank" rel="noopener noreferrer">Nodejs.org</a>, you should be good.
 
 You'll also need access to an OpenShift environment or the Red Hat Container Development Kit (CDK) minishift environment. For this example, I'll be using minishift. You can find instructions on getting minishift up and running <a href="https://developers.redhat.com/products/cdk/hello-world/" target="_blank" rel="noopener noreferrer">here</a>. For my local minishift, I start it with this command:
-<pre>$ minishift start --memory=6144 --vm-driver virtualbox</pre>
+
+`$ minishift start --memory=6144 --vm-driver virtualbox`
+
 You also need to be logged in to whatever OpenShift cluster you are using (OpenShift or minishift) using <code>oc login</code>.
 <h3>Spoiler Alert</h3>
 For those who don't want to read the whole post and don't want to scroll to the end, here are the three commands that need to be run:
-<pre>$ npx express-generator .</pre>
-<pre>$ npx json -I -f package.json -e 'this.scripts.start="PORT=8080 node ./bin/www"'</pre>
-<pre>$ npx nodeshift --strictSSL=false --expose</pre>
+
+`$ npx express-generator . `
+
+`$ npx json -I -f package.json -e 'this.scripts.start="PORT=8080 node ./bin/www"'`
+
+`$ npx nodeshift --strictSSL=false --expose`
+
 <h3>Generate an Express App</h3>
 What is Express, you say? Well, according to the <a href="https://expressjs.com/" target="_blank" rel="noopener noreferrer">Express website</a>, Express is a "Fast, unopinionated, minimalist web framework for Node.js."
 
 One pretty cool thing about Express is the <i>Express application generator tool</i>: <code>express-generator</code>. This is a command-line tool that <a href="https://expressjs.com/en/starter/generator.html">"quickly creates an application skeleton"</a>. But wait: didn't I just say that Express was unopinionated? It is, but this is the opinionated skeleton creator. ¯_(ツ)_/¯
 
 The Express website recommends installing the <code>express-generator</code> module globally, like this:
-<pre>npm install -g express-generator</pre>
+
+`npm install -g express-generator`
+
 But we aren't going to do that. Instead, we are going to use a fairly new feature from npm, called <code>npx</code>.
 
 <code>npx</code> gives us the ability to run one-off commands with out having to install things globally. There is more to <code>npx</code> that just that feature, so if you are interested in all the cool things <code>npx</code> can do, check it out <a href="https://medium.com/@maybekatz/introducing-npx-an-npm-package-runner-55f7d4bd282b">here</a>.
 
 With this new-found knowledge, we can now generate our Express app like this:
-<pre>$ npx express-generator .</pre>
+
+`$ npx express-generator .`
+
 Let's take a quick look at what is actually happening with this command. First, <code>npx</code> sees that we want to run the <code>express-generator</code> command, so <code>npx</code> does some magic to see if we have it installed locally (in our current directory), and then it checks our global modules. Because it is not there, it downloads it for this one-time use.
 
-<code>express-generator</code> is run in our current directory, which is denoted by that <strong>.</strong> at the end of the command.
+<code>express-generator</code> is run in our current directory, which is denoted by that **.** at the end of the command.
 
 The result should look something like this:
 
@@ -50,7 +57,9 @@ Now that we created our basic Express application using one command, we need to
 We need to pass a <code>PORT</code> environment variable to our start script.
 
 One way to do this is to open a text editor and do it that way, but that would add a few more steps. To do this in one command, we can use the <a href="https://www.npmjs.com/package/json" target="_blank" rel="noopener noreferrer">json module</a>.
-<pre>$ npx json -I -f package.json -e 'this.scripts.start="PORT=8080 node ./bin/www"'</pre>
+
+`$ npx json -I -f package.json -e 'this.scripts.start="PORT=8080 node ./bin/www"'`
+
 As before, we are using the <code>npx</code> command to allow us to not have to install the <code>json</code> module globally.
 
 Let's see what is going on with the options passed to the <code>json</code> module.
@@ -60,7 +69,9 @@ Let's see what is going on with the options passed to the <code>json</code> modu
 For more information on the <code>json</code> module, check out the <a href="http://trentm.com/json/">documentation</a>.
 <h3>Deploy the Application to OpenShift</h3>
 And now, the final step is to run this command:
-<pre>$ npx nodeshift --strictSSL=false --expose</pre>
+
+`$ npx nodeshift --strictSSL=false --expose`
+
 Here, we are using the <a href="https://www.npmjs.com/package/nodeshift" target="_blank" rel="noopener noreferrer">nodeshift module</a> to deploy our application. <code>nodeshift</code> is a CLI or programmable API that helps with deploying Node apps to OpenShift.
 
 <code>npx</code> is doing the same thing as in the previous examples.
@@ -81,15 +92,25 @@ Then, if we click the link, we can see our example app running:
 
 <img class="alignnone size-full wp-image-475737" src="https://developers.redhat.com/blog/wp-content/uploads/2018/03/express-quick-example-express.png" alt="" />
 
-<strong>Note:</strong> The example above will use the latest <a href="https://hub.docker.com/r/bucharestgold/centos7-s2i-nodejs/">community s2i images</a> (9.x at the time of this writing). To use a fully supported version of Node.js on OpenShift all you need is to add the "--dockerImage" flag.
+__Note:__ The example above will use the latest <a href="https://hub.docker.com/r/bucharestgold/centos7-s2i-nodejs/">community s2i images</a> (9.x at the time of this writing). To use a fully supported version of Node.js on OpenShift all you need is to add the "--dockerImage" flag.
 
 This will integrate the Red Hat OpenShift Application Runtime version Node.js (8.x) which you can get full production and developer support as part of our product subscription.
 
 This might look something like this:
-<pre>$ npx nodeshift --strictSSL=false --expose --dockerImage=registry.access.redhat.com/rhoar-nodejs/nodejs-8</pre>
+
+`$ npx nodeshift --strictSSL=false --expose --dockerImage=registry.access.redhat.com/rhoar-nodejs/nodejs-8`
+
 <h3>Recap</h3>
 In this post, the commands were a little spread out, so let's see them all together again:
-<pre>$ npx express-generator .</pre>
-<pre>$ npx json -I -f package.json -e 'this.scripts.start="PORT=8080 node ./bin/www"'</pre>
-<pre>$ npx nodeshift --strictSSL=false --expose</pre>
+
+`$ npx express-generator .`
+
+`$ npx json -I -f package.json -e 'this.scripts.start="PORT=8080 node ./bin/www"'`
+
+`$ npx nodeshift --strictSSL=false --expose`
+
 The example app we created was very simple, but it shows how quickly you can get started using Node.js on OpenShift.
+
+_(Edit: November 22, 2019) The Node images used in this post, both community centos7 and product, are no longer being updated and maintained. For community images, please use the Universal Base Image (UBI)-based node images located here: <a href="http://registry.access.redhat.com/ubi8/nodejs-10">registry.access.redhat.com/ubi8/nodejs-10</a>_
+
+_For a fully supported Product version of Node.js, please check out the Red Hat Software Collections Node.js image, <a href="https://access.redhat.com/containers/#/registry.access.redhat.com/rhscl/nodejs-10-rhel7">RH SCL Node.js</a>._