sharpred · sharpred · Oct 1, 2020 · Oct 1, 2020
diff --git a/.github/workflows/check.yml b/.github/workflows/check.yml
@@ -1,26 +1,16 @@
-# This is a basic workflow to help you get started with Actions
-
 name: CI
 
-# Controls when the action will run. Triggers the workflow on push or pull request
-# events but only for the master branch
 on:
   pull_request:
     branches: [ master ]
 
-# A workflow run is made up of one or more jobs that can run sequentially or in parallel
 jobs:
-  # This workflow contains a single job called "build"
   buildandhtmlproof:
-    # The type of runner that the job will run on
     runs-on: self-hosted
 
-    # Steps represent a sequence of tasks that will be executed as part of the job
     steps:
-    # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
     - uses: actions/checkout@v2
 
-    # Runs a single command using the runners shell
     - name: install prerequisites
       run: gem install minima jekyll html-proofer
 

diff --git a/Gemfile b/Gemfile
@@ -1,24 +1,8 @@
 source "https://rubygems.org"
 ruby RUBY_VERSION
 
-# Hello! This is where you manage which Jekyll version is used to run.
-# When you want to use a different version, change it below, save the
-# file and run `bundle install`. Run Jekyll with `bundle exec`, like so:
-#
-#     bundle exec jekyll serve
-#
-# This will help ensure the proper Jekyll version is running.
-# Happy Jekylling!
 gem "jekyll"
+gem 'jekyll-watch'
 
-# This is the default theme for new Jekyll sites. You may change this to anything you like.
 gem "minima"
 gem "html-proofer"
-# If you want to use GitHub Pages, remove the "gem "jekyll"" above and
-# uncomment the line below. To upgrade, run `bundle update github-pages`.
-#gem "github-pages", group: :jekyll_plugins
-
-# If you have any plugins, put them here!
-# group :jekyll_plugins do
-#   gem "jekyll-github-metadata", "~> 1.0"
-# end
diff --git a/README.md b/README.md
@@ -3,7 +3,5 @@ blog site
 
 ## running locally
 
-I have had issues getting incremental builds to play nice, so I create an article and then `bundle exec jekyll build` before serving as detailed below.
-
-Execute `bundle exec jekyll serve --incremental` to run this site locally. This will run the site at http://127.0.0.1:4000
+In a terminal window `bundle exec jekyll build --watch` before running `bundle exec jekyll serve --incremental` in a separate window.  This will run the site at http://127.0.0.1:4000
 
diff --git a/_config.yml b/_config.yml
@@ -1,9 +1,9 @@
 title: Sharpred
 email: paul@sharpred.com
 description: > # this means to ignore newlines until "baseurl:"
-  Personal site for Paul Ryan.
+  Paul Ryan, Mobile App Developer
 baseurl: "" # the subpath of your site, e.g. /blog
-url: "http://example.com" # the base hostname & protocol for your site
+url: "https://sharpred.com" # the base hostname & protocol for your site
 twitter_username: sharpred
 github_username:  sharpred
 
@@ -12,5 +12,6 @@ markdown: kramdown
 theme: minima
 # from https://jekyllrb.com/docs/continuous-integration/
 exclude: [vendor, gcp, google575963d4adf7f984.html]
-# from http://jmcglone.com/guides/github-pages/
-#permalink: /blog/:year/:month/:day/:title
+
+# Google services
+google_analytics: UA-179410290-1
diff --git a/_includes/analytics.html b/_includes/analytics.html
@@ -0,0 +1,8 @@
+(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');
+
diff --git a/_includes/head.html b/_includes/head.html
@@ -0,0 +1,10 @@
+<head>
+
+    <!-- Your head content -->
+
+    {% if jekyll.environment == 'production' %}
+    {% include analytics.html %}
+    {% endif %}
+
+    </head>
+
diff --git a/_posts/2020-08-19-amending a pipeline.md b/_posts/2020-08-19-amending a pipeline.md
@@ -85,5 +85,10 @@ it('This should pass', () => {
 })
 ```
 
-Commit your changes and push them to Github.
+Commit your changes and push them to Github. After a couple of minutes, your changes should trigger another pipeline job and this time it should run successfully.
 
+Congratulations! you have just completed your first pipeline amendment.  Remember to back up your Go Server and create a new Docker image with the resultant backup. Refer back to [here](/2020/07/09/adding-a-pipeline.html) if you need a refresher on how to do this.
+
+Next Time
+
+Next time we will look at deploying our application from a Go Server pipeline.
diff --git a/_posts/2020-10-01-deploying an application from a pipeline.md b/_posts/2020-10-01-deploying an application from a pipeline.md
@@ -0,0 +1,11 @@
+---
+layout: post
+title: Deploying an application from a Go Server pipeline
+author: Paul Ryan
+summary: Deploying an application from a Go Server pipeline
+date: 2020-10-01
+---
+
+**Introduction**
+
+//TODO
diff --git a/favicon.ico b/favicon.ico
diff --git a/index.html b/index.html
@@ -1,6 +1,6 @@
 ---
 layout: default
-title: Paul Ryan, Mobile App Consultant
+title: Paul Ryan, Mobile App Developer
 ---
 <div class="blurb">
 	<h1>Welcome</h1>