<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>DevOps on scarbrough.co.uk</title>
    <link>/categories/devops/</link>
    <description>Recent content in DevOps on scarbrough.co.uk</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 28 Mar 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="/categories/devops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fixing the Expired TLS/SSL Certificate Problem</title>
      <link>/post/security/certbot/</link>
      <pubDate>Thu, 28 Mar 2024 00:00:00 +0000</pubDate>
      <guid>/post/security/certbot/</guid>
      <description>Something broke the default TLS/SSL certificate for my primary site (scarbrough.co.uk) the other week, and browsers started flagging it as unsafe, which really didn&amp;rsquo;t look good. I figure it had something to do with my inadvertently deleting the /wwwroot/.well-known directory and whatever it contained.&#xA;Whatever the case, it was something I needed to fix myself, with a quick workaround until I had enough spare time to get a handle on how to generate a valid Let&amp;rsquo;s Encrypt certificate using Certbot.</description>
    </item>
    <item>
      <title>Dependency scanning tools as solutions to a different problem</title>
      <link>/post/development/dependency-scanning/</link>
      <pubDate>Thu, 09 Mar 2023 00:00:00 +0000</pubDate>
      <guid>/post/development/dependency-scanning/</guid>
      <description>Since dependency vulnerability scanning has been suggested by colleagues as something that could help with security/standards compliance and addressing legacy software, I&amp;rsquo;ve been looking into a few services to see how useful the available options could be.&#xA;NPM Audit Dependency scanning is performed by default with the install command for later versions of NPM, and by default, the output of npm audit will show a few lines of relevant information about each package with a reported vulnerability - its rating, a brief description of the vulnerability and whether an update is available.</description>
    </item>
    <item>
      <title>Netlify CMS and Continuous Deployment for Hugo</title>
      <link>/post/development/netlify-cms-hugo/</link>
      <pubDate>Tue, 20 Sep 2022 00:00:00 +0000</pubDate>
      <guid>/post/development/netlify-cms-hugo/</guid>
      <description>Netlify CMS and Continuous Deployment for Hugo Having experimented with this, I think Netlify&amp;rsquo;s idea of tacking a CMS onto a static site generator is tailored for situations where multiple developers, through Continuous Deployment, are providing a corporate site for which the content is being edited by non-technical users. At least it appears that way, because it takes a lot of work to develop the site and configure the CMS for anything more generic than the template provided, and an individual developer working on this as a personal project would most likely dispense with the CMS entirely and modify the files in the /content directory themselves (I&amp;rsquo;ll explain why).</description>
    </item>
    <item>
      <title>Migrations Using Visual Studio SQL Server Database Project</title>
      <link>/post/development/sql-server-database-vs-project/</link>
      <pubDate>Thu, 15 Sep 2022 00:00:00 +0000</pubDate>
      <guid>/post/development/sql-server-database-vs-project/</guid>
      <description>Migrations Using Visual Studio SQL Server Database Project Setting Up the Migration Project Add a new project to the Visual Studio solution. This project will initially be empty, without assembly references or scaffold files - it appears everything is native to Visual Studio. To this we need to add the connection to the database the schema is to be imported from. There will be a menu option for &amp;lsquo;Import&amp;rsquo; -&amp;gt; &amp;lsquo;Database&amp;rsquo;.</description>
    </item>
  </channel>
</rss>
