<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Maintenance on James Montgomery</title>
    <link>https://gh-jamesmontgomery.github.io/pages-blog/categories/maintenance/</link>
    <description>Recent content in Maintenance on James Montgomery</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 14 Jul 2021 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://gh-jamesmontgomery.github.io/pages-blog/categories/maintenance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Migrating to Cloudflare Pages</title>
      <link>https://gh-jamesmontgomery.github.io/pages-blog/2021/07/migrating-to-cloudflare-pages/</link>
      <pubDate>Wed, 14 Jul 2021 00:00:00 +0000</pubDate>
      <guid>https://gh-jamesmontgomery.github.io/pages-blog/2021/07/migrating-to-cloudflare-pages/</guid>
      <description>&lt;h2 id=&#34;tl-dr&#34;&gt;TL; DR&lt;/h2&gt;&#xA;&lt;p&gt;I recently decided to evaluate Cloudflare as a static site hosting provider. This post covers my findings and migration from AWS Amplify.&lt;/p&gt;&#xA;&lt;h2 id=&#34;amplify-overview&#34;&gt;Amplify Overview&lt;/h2&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://gh-jamesmontgomery.github.io/pages-blog/2020/09/migrating-site-to-aws/&#34;&gt;Amplify configuration is unchanged from the previous migration post&lt;/a&gt;. The website is statically generated content built with &lt;a href=&#34;https://gohugo.io/&#34;&gt;Hugo&lt;/a&gt; (noted as Hugo assets in the diagram). Cloudflare provides a proxy to save on bandwidth and provide a CDN function.&lt;/p&gt;&#xA;&#xA;&#xA;&#xA;    &#xA;&#xA;    &#xA;    &#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;  &#xA;  &#xA;    &#xA;  &#xA;&#xA;&#xA;    &#xA;&#xA;    &lt;div class=&#34;box alt&#34;&gt;&#xA;        &lt;div class=&#34;row uniform&#34;&gt;&#xA;        &#xA;        &#xA;        &#xA;            &#xA;                &lt;div class=&#34;1u&#34;&gt;&#xA;            &#xA;            &#xA;        &#xA;            &#xA;                &#xA;                    &#xA;                    &lt;span class=&#34;image fit&#34;&gt;&#xA;                &#xA;            &#xA;            &#xA;        &#xA;            &#xA;                &#xA;                        &lt;img src=&#39;https://gh-jamesmontgomery.github.io/pages-blog/img/2021/07/CF-AWS-2021-06-15-0737.png&#39;&#xA;                            alt=&#34;How I combined AWS Amplify with Cloudflare&#34;&gt;&#xA;                    &lt;/span&gt;&lt;/div&gt;&#xA;                &#xA;                &#xA;            &#xA;            &#xA;        &#xA;        &lt;/div&gt;&#xA;    &lt;/div&gt;&#xA;&#xA;&#xA;&lt;p&gt;Besides providing hosting for &lt;code&gt;ja.mesmontgomery.co.uk&lt;/code&gt;, Amplify provides several redirects.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Migrating site to AWS</title>
      <link>https://gh-jamesmontgomery.github.io/pages-blog/2020/09/migrating-site-to-aws/</link>
      <pubDate>Mon, 21 Sep 2020 00:00:00 +0000</pubDate>
      <guid>https://gh-jamesmontgomery.github.io/pages-blog/2020/09/migrating-site-to-aws/</guid>
      <description>&lt;h2 id=&#34;tl-dr&#34;&gt;TL; DR&lt;/h2&gt;&#xA;&lt;p&gt;Some time ago, I decided to multi-cloud my site. I&amp;rsquo;ve recently decided to revert to a single cloud hosting provider. I&amp;rsquo;m taking the opportunity to experience Amplify static hosting for this site.&lt;/p&gt;&#xA;&lt;h2 id=&#34;challenges-with-the-previous-configuration&#34;&gt;Challenges with the previous configuration&lt;/h2&gt;&#xA;&lt;p&gt;Multiple hosting locations meant multiple build processes.&lt;/p&gt;&#xA;&#xA;&#xA;&#xA;    &#xA;&#xA;    &#xA;    &#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;  &#xA;  &#xA;    &#xA;  &#xA;&#xA;&#xA;    &#xA;&#xA;    &lt;div class=&#34;box alt&#34;&gt;&#xA;        &lt;div class=&#34;row uniform&#34;&gt;&#xA;        &#xA;        &#xA;        &#xA;            &#xA;                &lt;div class=&#34;1u&#34;&gt;&#xA;            &#xA;            &#xA;        &#xA;            &#xA;                &#xA;                    &#xA;                    &lt;span class=&#34;image fit&#34;&gt;&#xA;                &#xA;            &#xA;            &#xA;        &#xA;            &#xA;                &#xA;                        &lt;img src=&#39;https://gh-jamesmontgomery.github.io/pages-blog/img/2020/09/duelstack.jpeg&#39;&#xA;                            alt=&#34;Duel stack overview&#34;&gt;&#xA;                    &lt;/span&gt;&lt;/div&gt;&#xA;                &#xA;                &#xA;            &#xA;            &#xA;        &#xA;        &lt;/div&gt;&#xA;    &lt;/div&gt;&#xA;&#xA;&#xA;&lt;p&gt;In effect, the site was built, deployed (to Firebase) then rebuilt and redeployed (to AWS). Admittedly, the latter was rarely an overhead as the AWS Amplify CI/CD workflow was triggered upon commit to the master branch on CodeCommit.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Domain migration and enabling DNSSEC</title>
      <link>https://gh-jamesmontgomery.github.io/pages-blog/2019/09/domain-migration-and-enabling-dnssec/</link>
      <pubDate>Wed, 25 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://gh-jamesmontgomery.github.io/pages-blog/2019/09/domain-migration-and-enabling-dnssec/</guid>
      <description>&lt;h2 id=&#34;tl-dr&#34;&gt;TL; DR&lt;/h2&gt;&#xA;&lt;p&gt;The renewal date on my .co.uk domain was nearing. I decided to make a change from 123-reg to iwantmyname. After migration, I captured the process to enable DNSSEC when using Cloudflare for DNS. For those thinking of a similar migration, I have also documented my experience of moving to iwantmyname.&lt;/p&gt;&#xA;&lt;h2 id=&#34;couk-domain-registrar-migration-to-iwantmyname&#34;&gt;.co.uk domain registrar migration to iwantmyname&lt;/h2&gt;&#xA;&lt;p&gt;I had used iwantmyname previously and so benefitted from having an account already. After sign-in/signup the overview page has a link to allow a domain transfer to start:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
