<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>hugo on Computers Fear Me</title>
    <link>http://computersfearme.com/tags/hugo/</link>
    <description>Recent content in hugo on Computers Fear Me</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 25 Jun 2017 00:00:00 +0000</lastBuildDate><atom:link href="http://computersfearme.com/tags/hugo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automating Static Website Deployment, Part 2</title>
      <link>http://computersfearme.com/post/automate-website-updates-part2/</link>
      <pubDate>Sun, 25 Jun 2017 00:00:00 +0000</pubDate>
      
      <guid>http://computersfearme.com/post/automate-website-updates-part2/</guid>
      <description>&lt;p&gt;This is a continuation of a series of articles started in &lt;a href=&#34;http://computersfearme.com/post/automate-website-updates-part1/&#34;&gt;Part 1&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In this installment we will be discussing how I construct the &lt;a href=&#34;https://aws.amazon.com/codebuild/&#34;&gt;CodeBuild&lt;/a&gt;
buildspec.yml, and the &lt;a href=&#34;https://aws.amazon.com/codecommit/&#34;&gt;CodeCommit&lt;/a&gt; trigger that will invoke it.  First, however,
I will discuss the shortcommings of &lt;a href=&#34;https://aws.amazon.com/codepipeline/&#34;&gt;CodePipeline&lt;/a&gt; and
&lt;a href=&#34;https://aws.amazon.com/codedeploy/&#34;&gt;CodeDeploy&lt;/a&gt; that made them inappropriate for this usecase.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Automating Static Website Deployment, Part 1</title>
      <link>http://computersfearme.com/post/automate-website-updates-part1/</link>
      <pubDate>Sun, 11 Jun 2017 00:00:00 +0000</pubDate>
      
      <guid>http://computersfearme.com/post/automate-website-updates-part1/</guid>
      <description>&lt;p&gt;Now that I have 8 static websites deployed into AWS using S3 and CloudFront I need
to automate the deployment process so that I can make changes quickly and get them
to production with less effort.  To that end I have developed some scripts and
configurations that automate the deployment of this site to a QA environment and
production when changes are pushed to either branch.  I will be describing this
work in probably 3 parts.  This is the first.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Hosting a Static Website for Pennies a Month</title>
      <link>http://computersfearme.com/post/hosting-a-static-website-for-pennies-a-month/</link>
      <pubDate>Sat, 18 Feb 2017 00:00:00 +0000</pubDate>
      
      <guid>http://computersfearme.com/post/hosting-a-static-website-for-pennies-a-month/</guid>
      <description>For years I have been running a few very low traffic websites on various platforms. The first versions of these were run on a VM running LAMP that was costing me about $25.00 a month. About 3 years ago, I thought I could do better on cost and performance in EC2. So I bought a reserved t1.micro EC2 instance and a reserved t1.micro RDS instance both on a 3 year term.</description>
    </item>
    
  </channel>
</rss>
