<?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://ja.mesmontgomery.co.uk/categories/maintenance/</link>
    <description>Recent content in Maintenance on James Montgomery</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 14 Jul 2021 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ja.mesmontgomery.co.uk/categories/maintenance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Migrating to Cloudflare Pages</title>
      <link>https://ja.mesmontgomery.co.uk/2021/07/migrating-to-cloudflare-pages/</link>
      <pubDate>Wed, 14 Jul 2021 00:00:00 +0000</pubDate>
      <guid>https://ja.mesmontgomery.co.uk/2021/07/migrating-to-cloudflare-pages/</guid>
      <description>TL; DR I recently decided to evaluate Cloudflare as a static site hosting provider. This post covers my findings and migration from AWS Amplify.&#xA;Amplify Overview The Amplify configuration is unchanged from the previous migration post. The website is statically generated content built with Hugo (noted as Hugo assets in the diagram). Cloudflare provides a proxy to save on bandwidth and provide a CDN function.&#xA;Besides providing hosting for ja.mesmontgomery.co.uk, Amplify provides several redirects.</description>
    </item>
    <item>
      <title>Migrating site to AWS</title>
      <link>https://ja.mesmontgomery.co.uk/2020/09/migrating-site-to-aws/</link>
      <pubDate>Mon, 21 Sep 2020 00:00:00 +0000</pubDate>
      <guid>https://ja.mesmontgomery.co.uk/2020/09/migrating-site-to-aws/</guid>
      <description>TL; DR 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.&#xA;Challenges with the previous configuration Multiple hosting locations meant multiple build processes.&#xA;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.</description>
    </item>
    <item>
      <title>Domain migration and enabling DNSSEC</title>
      <link>https://ja.mesmontgomery.co.uk/2019/09/domain-migration-and-enabling-dnssec/</link>
      <pubDate>Wed, 25 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://ja.mesmontgomery.co.uk/2019/09/domain-migration-and-enabling-dnssec/</guid>
      <description>TL; DR 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.&#xA;.co.uk domain registrar migration to iwantmyname I had used iwantmyname previously and so benefitted from having an account already.</description>
    </item>
  </channel>
</rss>
