<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sebastian Rogers on Medium]]></title>
        <description><![CDATA[Stories by Sebastian Rogers on Medium]]></description>
        <link>https://medium.com/@sebastian-rogers?source=rss-b2b2635f60cd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*EuWBuFlLQUVUVeFJuPxhEg.jpeg</url>
            <title>Stories by Sebastian Rogers on Medium</title>
            <link>https://medium.com/@sebastian-rogers?source=rss-b2b2635f60cd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:00:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sebastian-rogers/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Not By The Book: Banjo By Beginners]]></title>
            <link>https://medium.com/banjo-by-a-beginner/not-by-the-book-banjo-by-beginners-44ffd97aa828?source=rss-b2b2635f60cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/44ffd97aa828</guid>
            <category><![CDATA[music-education]]></category>
            <category><![CDATA[beginner]]></category>
            <category><![CDATA[self-taught]]></category>
            <category><![CDATA[banjo]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Sebastian Rogers]]></dc:creator>
            <pubDate>Wed, 12 Aug 2026 10:55:41 GMT</pubDate>
            <atom:updated>2026-11-16T09:01:03.301Z</atom:updated>
            <content:encoded><![CDATA[<p>Continuing the series on how I learnt to play the banjo, or at least a passing resemblance to playing if the audience know nothing about the finer, or grosser, points of banjo picking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*rm93DRBMzfKlj1hI.jpeg" /><figcaption>My Banjo Bookcase</figcaption></figure><p>When I started playing banjo I just bought a banjo, over the phone. I’ll be honest I have no idea why other than I wanted to play an instrument and my brother is an accomplished guitarist and bass player, my father was a piano player and played double bass and I wanted to do something different. So I bought a banjo. It came with a book that I tried to learn from. I bought other books to help me learn.</p><p>Now seven years later I have a shelf full of books, some of them beginners guides, some of them specialist manuals, some of them just tab, or even fake books. I’ll review many of them in detail as this series goes on.</p><p>For now I want to talk about the first one I had. Not in detail but why it was the start of learning how not to learn.</p><p>This is not a bad book, far from it, and it has good stuff in it but I couldn’t learn to play from it, my fault. I followed its advice and did the exercises and listened to and played along to the practice tracks, I did twenty minutes a day, I got to page 27 and after three months I packed the banjo up and it sat there for many years, unused and unloved. At this point I could do a couple of roll patterns and a few chords, I could even play a few simple songs. I knew I was doing it correctly but somehow it wasn’t music. The one thing the book hadn’t dealt with was what is music and how do you recognise it when you hear it. It laid out the basics but assumed you knew what you wanted as a goal. In essence I had put my trail boots on gone out, grabbed a route map, for a nice little ramble and when I’d seen a couple of things I didn’t know what to do so I stopped. It would take many years and five specific incidents before I knew where I was going, each one of which changed my course.</p><ul><li>My wife bought me in person collective banjo lessons</li><li>I went to a jam session</li><li>I met Ron Block</li><li>I joined a band</li><li>I helped form a band</li></ul><p>However now I’m straying into next week’s topic.</p><p>That’s it for now, Y’all come back now, y’hear?</p><p>Sebastian</p><p><em>Originally published at </em><a href="https://medium.com/@banjosandwichband/not-by-the-book-banjo-by-beginners-b15c05404fdf"><em>https://medium.com</em></a><em> as Banjo Sandwich on August 12, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44ffd97aa828" width="1" height="1" alt=""><hr><p><a href="https://medium.com/banjo-by-a-beginner/not-by-the-book-banjo-by-beginners-44ffd97aa828">Not By The Book: Banjo By Beginners</a> was originally published in <a href="https://medium.com/banjo-by-a-beginner">Banjo by a Beginner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Begin at the Ending]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/banjo-by-a-beginner/begin-at-the-ending-c2a9a19b0067?source=rss-b2b2635f60cd------2"><img src="https://cdn-images-1.medium.com/max/755/0*wCTrpyhf9lmJOss2.png" width="755"></a></p><p class="medium-feed-snippet">Continuing the series on how I learnt to play the banjo, or at least a passing resemblance to playing if the audience know nothing about&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/banjo-by-a-beginner/begin-at-the-ending-c2a9a19b0067?source=rss-b2b2635f60cd------2">Continue reading on Banjo by a Beginner »</a></p></div>]]></description>
            <link>https://medium.com/banjo-by-a-beginner/begin-at-the-ending-c2a9a19b0067?source=rss-b2b2635f60cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2a9a19b0067</guid>
            <category><![CDATA[banjo]]></category>
            <category><![CDATA[bluegrass]]></category>
            <category><![CDATA[beginner]]></category>
            <category><![CDATA[musicianship]]></category>
            <category><![CDATA[listening]]></category>
            <dc:creator><![CDATA[Sebastian Rogers]]></dc:creator>
            <pubDate>Wed, 05 Aug 2026 10:12:59 GMT</pubDate>
            <atom:updated>2026-11-14T09:01:04.025Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[First Things First]]></title>
            <link>https://medium.com/banjo-by-a-beginner/first-things-first-banjo-by-beginner-3ac65382d2ee?source=rss-b2b2635f60cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ac65382d2ee</guid>
            <category><![CDATA[beginner]]></category>
            <category><![CDATA[musicianship]]></category>
            <category><![CDATA[visualization]]></category>
            <category><![CDATA[mental-practice]]></category>
            <category><![CDATA[banjo]]></category>
            <dc:creator><![CDATA[Sebastian Rogers]]></dc:creator>
            <pubDate>Tue, 21 Jul 2026 10:36:44 GMT</pubDate>
            <atom:updated>2026-11-12T09:39:51.872Z</atom:updated>
            <content:encoded><![CDATA[<p>So the purpose of these posts is to give a bit of a potted history of how I’ve learnt to play the banjo, so far, and talk about things I did which were good ideas, bad ideas, pointless ideas and bat shit crazy ideas. I’ll include things I did, things I’ve read or watched that were helpful and hopefully it will entertain and educate people who can play the banjo or hope to play it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*PQmM8VdfpZfl95mO.jpeg" /><figcaption>A group of absolute beginners</figcaption></figure><p>I’m going to start with what you need to be able to play the banjo.</p><p>That is truly all you need and the order is not random. Lets walk them through one at a time.</p><h3>Mind</h3><p>This is the only one you actually need and its the most important. In effect playing the banjo is really the process of conjuring up the sound you wish to hear inside your mind and then translating that via your body and the banjo to the outside world.</p><p>Without this first step, imagining the sound, the whole project is doomed to failure. There are ways to compensate by using sight, in the form of reading notation, or touch, in the form of remembering where to put your fingers, but these are very hard to do and they lack fluency. If you want to play your instrument rather than be a lack lustre record player replacement you need to be able to do this hear the sound in your mind and then ‘without thinking’ move your body so your instrument produces that sound.</p><p>This is a rant for another day but let me formulate Sebastian’s First Hard Won Rule of Learning to Play the Banjo.</p><blockquote><em>To play in the real world you must first be able to play in your imagination.</em></blockquote><p>The upshot of this is that you can do real learning just in your head and in fact this is probably the most important type of learning you’ll ever do.</p><h3>Body</h3><p>Once you can imagine what you want to play inside your then you need to make it happen outside your head. For this you need less than you think. I’ve played with people who are missing lots of different body parts, including fingers on their left hand, or who have medical issues that prevent them from holding their instrument in the ‘normal’ way.</p><p>You don’t need a great body that responds superbly and naturally executes your desires, you just need one that has minimal movement and flexibility. Practice will eventually allow your body to respond in the way you need it to.</p><p>There are lots of counter-intuitive things you can do to make it easier for your body to act in the way you want and its worth knowing these things early so you don’t have to learn them later.</p><h3>Banjo</h3><p>You could play any instrument, or even none, but you have wisely selected the banjo so you’ll need to beg, borrow or steal one, or maybe buy one.</p><p>There’s a huge amount to talk about with regards to banjos but these are not guitars.</p><blockquote><em>A banjo is a semi-random collection of parts disguised as a working instrument.</em></blockquote><p>However there are different types of banjo and having the type that suits what the style you want to play most will help. All banjos are fully chromatic so any banjo can play any tune however…</p><ul><li>Use a five string with resonator for Bluegrass</li><li>Use a five string without a resonator for Clawhammer</li><li>Use a four string for Traditional Irish</li><li>Use a six string because you really want to be a guitar player</li></ul><p>That’s it for now, Y’all come back now, y’hear?</p><p>Sebastian</p><p><em>Originally published at </em><a href="https://medium.com/@banjosandwichband/first-things-first-banjo-by-beginner-ad022e8c41f6"><em>https://medium.com</em></a><em> as banjosandwichband on July 21, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ac65382d2ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/banjo-by-a-beginner/first-things-first-banjo-by-beginner-3ac65382d2ee">First Things First</a> was originally published in <a href="https://medium.com/banjo-by-a-beginner">Banjo by a Beginner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure Static Web Apps: The ‘FUNCTIONS_WORKER_RUNTIME’ setting is required.]]></title>
            <link>https://sebastian-rogers.medium.com/azure-static-web-apps-the-functions-worker-runtime-setting-is-required-7583d7470a4a?source=rss-b2b2635f60cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/7583d7470a4a</guid>
            <category><![CDATA[azure-static-web-app]]></category>
            <category><![CDATA[debugging]]></category>
            <dc:creator><![CDATA[Sebastian Rogers]]></dc:creator>
            <pubDate>Fri, 10 May 2024 08:04:50 GMT</pubDate>
            <atom:updated>2024-05-10T08:04:50.901Z</atom:updated>
            <content:encoded><![CDATA[<h3>Azure Static Web Apps: The ‘FUNCTIONS_WORKER_RUNTIME’ setting is required. Please specify a valid value.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*AQhUvVfyz13tHgXFfHeo3Q.png" /></figure><p><em>TL;DR You need to create a local.settings.json file with the FUNCTIONS_WORKER_RUNTIME setting.</em></p><p>Nice simple one this to remove this warning message when running Azure Static Web Apps locally create a local.settings.json file in your api folder and add the following:</p><pre>{<br>  &quot;IsEncrypted&quot;: false,<br>  &quot;Values&quot;: {<br>    &quot;FUNCTIONS_WORKER_RUNTIME&quot;: &quot;node&quot;<br>  }<br>}</pre><p>This also deals with several other issues the API has with being node, like not knowing what type of build to use.</p><p><em>TL;CR You need to create a local.settings.json file with the FUNCTIONS_WORKER_RUNTIME setting.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7583d7470a4a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Easy ways to capture PowerShell output: 1 Start-Transcript]]></title>
            <link>https://sebastian-rogers.medium.com/easy-ways-to-capture-powershell-output-1-start-transcript-db58762a6aed?source=rss-b2b2635f60cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/db58762a6aed</guid>
            <category><![CDATA[powershell]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Sebastian Rogers]]></dc:creator>
            <pubDate>Thu, 22 Feb 2024 10:46:21 GMT</pubDate>
            <atom:updated>2024-02-22T10:46:21.909Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*AQhUvVfyz13tHgXFfHeo3Q.png" /></figure><p><em>TL;DR Don’t write directly to files in PowerShell, use Start-Transcript instead.</em></p><p>Its common when running scripts to need to provide output of what happened, especially when doing bulk operations or DEVOps. This can either be to prove that it happened or for diagnostics when things go wrong.</p><p>You could add to all your scripts logging that writes directly to a file but that’s not a good idea.</p><ul><li>You have to add it to every command you write.</li><li>It won’t cover native PowerShell commands.</li><li>It won’t cover commands in other people’s modules.</li><li>You don’t need to because Start-Transcript exists.</li></ul><p>This handy command in the <a href="https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.host/?view=powershell-7.4">Microsoft.PowerShell.Host</a> module writes out the commands and their output to a text file. See <a href="https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.host/start-transcript?view=powershell-7.4">Start-Transcript</a> for full details. When your done use <a href="https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.host/stop-transcript?view=powershell-7.4">Stop-Transcript</a>.</p><p>You can even set this up in your <a href="https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_profiles?view=powershell-7.4">PowerShell Profile</a> so its just on all the time. I do this with PRODUCTION cloud shells so that there are no questions about what was actually done.</p><p>Useful, and not so useful parameters,</p><ul><li>IncludeInvocationHeader, adds a timestamp before each command</li><li>OutputDirectory, specify a folder for the transcript I prefer this to path.</li><li>Path, lets you specify exactly what the transcript is called but the default naming convention is pretty good and avoids name clashes.</li></ul><p>Enjoy.</p><p><em>TL;CR Don’t write directly to files in PowerShell, use Start-Transcript instead.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db58762a6aed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure Static Web App: I don’t want the app in the root of my project]]></title>
            <link>https://sebastian-rogers.medium.com/azure-static-web-app-i-dont-want-the-app-in-the-root-of-my-project-47bc4e0fdd6e?source=rss-b2b2635f60cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/47bc4e0fdd6e</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[azure-static-web-app]]></category>
            <category><![CDATA[best-practices]]></category>
            <dc:creator><![CDATA[Sebastian Rogers]]></dc:creator>
            <pubDate>Thu, 08 Feb 2024 12:28:41 GMT</pubDate>
            <atom:updated>2024-02-08T12:28:41.647Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*AQhUvVfyz13tHgXFfHeo3Q.png" /></figure><p><em>TL;DR You need to change the YAML file as well as the folder.</em></p><p>If you’ve been following along with me on how to use <a href="https://learn.microsoft.com/en-us/azure/static-web-apps/overview">Azure Static Web Apps</a> we have already looked at:</p><ul><li><a href="https://medium.com/@sebastian-rogers/azure-static-web-app-codespaces-wont-load-local-development-8844b02450ae">Azure Static Web App: CodeSpaces won’t load local development</a></li><li><a href="https://medium.com/@sebastian-rogers/azure-static-web-app-error-error-0308010c-digital-envelope-routines-unsupported-0586f1b75726">Azure Static Web App: “Error: error:0308010C:digital envelope routines::unsupported”</a></li></ul><p>The OOTB <a href="https://learn.microsoft.com/en-us/azure/static-web-apps/deploy-react?pivots=github">React example for Azure Static Web Apps</a> is fine but its simple, a little too simple and one of the things it does is host the App directly in the root of the project and thus not separate the App from the API.</p><p>I think they’ve done this to keep things ‘simple’ so users can easily find the relevant parts, and the example does not use an API, but in practice when using a repository having code directly off the root means that it can only hold one component easily and any other components then have to be isolated via configuration.</p><p>In practice any but the most simple Web Sites will have a front end, the App, which is essentially static, and one or more back ends, the APIs, that provide active, i.e. state dependent data.</p><p>However often these front ends and back ends are tightly bound and unless you’re providing a generic utility API linked to a publicly available service it makes sense to keep them in a single repository, and maybe use something like <a href="https://trpc.io/">tRPC</a> to provide a type safe contract between them.</p><p>There’s some things you’ll need to do for this to happen.</p><ol><li>Move all of the App files into a separate app folder</li><li>Modify the .github/workflows/*.yml file to reference this folder</li><li>Modify the swa-cli.config.json file to reference this folder</li></ol><p>For a fully worked example see <a href="https://github.com/Simple-Innovation/my-first-static-web-app">Simple-Innovation/my-first-static-web-app (github.com)</a>.</p><h4>App Files and Folders</h4><p>Move the following root level files into a folder, I use app as it fits nicely with api, which is used, by default, to host the API files.</p><ol><li>build</li><li>public</li><li>src</li><li>.gitignore</li><li>package-lock.json</li><li>package.json</li><li>staticwebapp.config.json</li></ol><h4>YML File</h4><p>In the .github/workflows folder you’ll find a yml file.</p><p>You need to update this so that the Azure Static Web App deployment tools know where to find the files.</p><p>In jobs &gt; build_and_deploy_job &gt; steps: -name Build And Deploy &gt; with &gt; app_location set the value to the name of the folder, e.g. app</p><h4>swa-cli.config.json</h4><p>You need to update this so that the Azure Static Web App local rnuntime tools know where to find the files.</p><p>In configurations &gt; app name &gt; appLocation set the value to the name of the folder, e.g. app</p><h4>Tidy Up</h4><p>If you have built the project before you must delete the root node_modules folder or it will get committed to the repository as a result of you moving the .gitignore file.</p><h4>Build Locally</h4><p>As we don’t have an API, yet, we can just build via the Azure Static Web Apps CLI.</p><pre>swa build</pre><h4>Run Locally</h4><p>As we don’t have an API, yet, we can just run via the Azure Static Web Apps CLI.</p><pre>swa start</pre><h4>Deploy</h4><p>I’d just commit your changes and push them to the Repository, Azure Static Web Apps will take care of the rest.</p><p><em>TL;DR You need to change the YAML file as well as the folder.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47bc4e0fdd6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure Static Web App: CodeSpaces won’t load local development]]></title>
            <link>https://sebastian-rogers.medium.com/azure-static-web-app-codespaces-wont-load-local-development-8844b02450ae?source=rss-b2b2635f60cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/8844b02450ae</guid>
            <category><![CDATA[dns]]></category>
            <category><![CDATA[github-codespaces]]></category>
            <category><![CDATA[redirect]]></category>
            <dc:creator><![CDATA[Sebastian Rogers]]></dc:creator>
            <pubDate>Thu, 25 Jan 2024 17:13:43 GMT</pubDate>
            <atom:updated>2024-01-25T17:13:43.334Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*AQhUvVfyz13tHgXFfHeo3Q.png" /></figure><p><em>TL;DR You need to use an external DNS if you want localhost redirection to work for GitHub CodeSpaces.</em></p><p>If your using, and enjoying, <a href="https://learn.microsoft.com/en-us/azure/static-web-apps/overview">Azure Static Web Apps</a> and have got React working with them, see my previous story <a href="https://medium.com/@sebastian-rogers/azure-static-web-app-error-error-0308010c-digital-envelope-routines-unsupported-0586f1b75726">Azure Static Web App: “Error: error:0308010C:digital envelope routines::unsupported” — Sebastian Rogers — Medium</a>, you may want to lighten the load on your laptop and use <a href="https://code.visualstudio.com/docs/remote/codespaces">GitHub CodeSpaces</a> to develop them in. The ability to spin up and then throw away whole development environments almost completely isolated from the machine you use is fantastic. For example you may work for an organisation with strict policies about what can be installed on your machine but CodeSpaces run in the browser so you can use them on such a restricted device. I’ve even done changes via CodeSpaces to code using my mobile phone.</p><p>However when you come to local development then you start interacting with the machine the browser is running on as all Http requests need to be redirected. For most people this won’t cause an issue as you’ll be using a DNS server not hosted on the machine hosting the CodeSpace and everything will just work. If your DNS settings are set to use the local machine though all requests fail to redirect and instead timeout.</p><p>The solution is simple just configure your host machine to use an external DNS, you can get a list of reputable DNS servers from here <a href="https://public-dns.info/nameserver/gb.html">DNS servers in United Kingdom</a>.</p><p>Then set the DNS settings for your local network connection, here’s a good explanation of how to do it <a href="https://helpdeskgeek.com/networking/change-ip-address-and-dns-servers-using-the-command-prompt/">Change IP Address and DNS Servers using the Command Prompt (helpdeskgeek.com)</a></p><p><em>TL;CR You need to use an external DNS if you want localhost redirection to work for GitHub CodeSpaces.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8844b02450ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure Static Web App: “Error: error:0308010C:digital envelope routines::unsupported”]]></title>
            <link>https://sebastian-rogers.medium.com/azure-static-web-app-error-error-0308010c-digital-envelope-routines-unsupported-0586f1b75726?source=rss-b2b2635f60cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/0586f1b75726</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[static-web-app]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[error]]></category>
            <dc:creator><![CDATA[Sebastian Rogers]]></dc:creator>
            <pubDate>Tue, 16 Jan 2024 10:15:07 GMT</pubDate>
            <atom:updated>2024-01-16T10:15:07.159Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*AQhUvVfyz13tHgXFfHeo3Q.png" /></figure><p><em>TL;DR You need the latest copy of react scripts installed to avoid the error:0308010C:digital envelope routines::unsupported.</em></p><p>The <a href="https://learn.microsoft.com/en-us/azure/static-web-apps/overview">Azure Static Web Apps</a> are great for quickly creating systems for prototyping or testing ideas and the documentation is pretty good too.</p><p>However they have a few problems, not least of which is that out of the box if you try and build the React starter app you’ll get the error message:</p><blockquote>Error: error:0308010C:digital envelope routines::unsupported</blockquote><p>Fortunately the fix is simple enough, thank you <a href="https://stackoverflow.com/a/71334532/3629917">Stack Overflow</a>, just update the create react app scripts.</p><blockquote>npm i react-scripts@latest</blockquote><p>Then build it again</p><blockquote>npm run build</blockquote><p>And the issue will go away</p><p><em>TL;CR You need the latest copy of react scripts installed to avoid the error:0308010C:digital envelope routines::unsupported.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0586f1b75726" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Today’s Technical Terms: Truss]]></title>
            <link>https://sebastian-rogers.medium.com/todays-technical-terms-truss-460f7c80b249?source=rss-b2b2635f60cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/460f7c80b249</guid>
            <category><![CDATA[acronyms]]></category>
            <category><![CDATA[irony]]></category>
            <dc:creator><![CDATA[Sebastian Rogers]]></dc:creator>
            <pubDate>Wed, 01 Nov 2023 11:08:28 GMT</pubDate>
            <atom:updated>2023-11-01T11:08:28.847Z</atom:updated>
            <content:encoded><![CDATA[<p>Number 1 in an occasional series of technical terminology we need but don’t have, yet.</p><h3>TRUSS (Noun)</h3><p>A application that suddenly gets promoted and uses its processing power to totally crash whatever its running on.</p><blockquote>Can you check that crashed server to find the TRUSS.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=460f7c80b249" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Orchestration modes for Virtual Machine Scale Sets in Azure]]></title>
            <link>https://sebastian-rogers.medium.com/orchestration-modes-for-virtual-machine-scale-sets-in-azure-e361610a5527?source=rss-b2b2635f60cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/e361610a5527</guid>
            <category><![CDATA[script]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[azure-scale-set]]></category>
            <category><![CDATA[virtual-machine]]></category>
            <dc:creator><![CDATA[Sebastian Rogers]]></dc:creator>
            <pubDate>Wed, 18 Oct 2023 10:49:15 GMT</pubDate>
            <atom:updated>2023-10-18T10:49:15.399Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*AQhUvVfyz13tHgXFfHeo3Q.png" /></figure><p><em>TL;DR You can now directly access the Azure VMs in a VM Scale Set if you select the right option when you create it.</em></p><p>Quick one, again as a result of something a client asked us to do.</p><blockquote>We have all these VMs in a scale set but we need to swap them to a new network, in this specific Azure environment, by the way each of them has been individually configured and has data we can’t lose on their C: drive.</blockquote><p>Now Virtual Machine Scale Sets were not really set up for this, they provide a way to scale, clue is in the name, a number of identical instances of machines, so its easy to create and destroy them. This is ideal if you have a set of stateless transactions or processes that are too heavy for an Azure Function or need access to something they don’t support, like a lot of on-premises software that needs an actual Windows OS to operate. These ‘uniform’ scale sets are ideal for this.</p><p>However the big drawback is because they are ‘all the same’ most of the Azure REST API, and hence all the other Command Line Tools and User Interfaces associated with Virtual Machines won’t work with them. They shouldn’t as they would let you customise each one.</p><p>However a while ago Microsoft introduced ‘flexible’ Scale Sets, see <a href="https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes">Orchestration modes for Virtual Machine Scale Sets in Azure — Azure Virtual Machine Scale Sets | Microsoft Learn</a>, which orchestrate the creation and destruction of Virtual Machines based on images but once created they are accessible to the Azure VM REST API and so can be manipulated like any other virtual machines, including swapping their OS disks.</p><p>These are ideal for most Azure VM workloads, as these days Azure Functions are the go to for automating stateless processes, and in fact are now the <a href="https://techcommunity.microsoft.com/t5/azure-compute-blog/breaking-change-for-vmss-powershell-cli-customers/ba-p/3818295">default </a>for any new Azure VM Scale Sets.</p><p>In addition each of the Azure VMs in the scale set can be seen directly in the Azure Resource Group, rather than being hidden in the Scale Set itself.</p><p>So in the end it was a case of creating a flexible scale set, creating an identical number of images to the original Virtual Machines, snapshotting the original Virtual Machines Disks and then swapping them into the new Virtual Machines.</p><p>If you’d like to see some code for this its here <a href="https://dev.azure.com/simpleinnovation/Azure%20VM%20Scale%20Set">Azure VM Scale Set</a>.</p><p><em>TL;CR You can now directly access the Azure VMs in a VM Scale Set if you select the right option when you create it.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e361610a5527" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>