<?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 Michael Villis on Medium]]></title>
        <description><![CDATA[Stories by Michael Villis on Medium]]></description>
        <link>https://medium.com/@mvillis?source=rss-a7c38140d775------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*lSLwioJI2VjfHWPU.</url>
            <title>Stories by Michael Villis on Medium</title>
            <link>https://medium.com/@mvillis?source=rss-a7c38140d775------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 16:02:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mvillis/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[Curiosity is king! And the launch of my reading list]]></title>
            <link>https://medium.com/bikebytes/curiosity-is-king-and-the-launch-of-my-reading-list-229777ffaeac?source=rss-a7c38140d775------2</link>
            <guid isPermaLink="false">https://medium.com/p/229777ffaeac</guid>
            <category><![CDATA[curiosity]]></category>
            <category><![CDATA[reading]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Michael Villis]]></dc:creator>
            <pubDate>Sun, 09 Jul 2017 11:54:37 GMT</pubDate>
            <atom:updated>2017-07-09T12:09:39.965Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>tl;dr</strong> —40 of my favourite articles are here <a href="https://www.mikevillis.com/reading">https://www.mikevillis.com/reading</a>. I hope you find them as interesting as I did!</p><p>I recently completed a <a href="https://www.viacharacter.org/www/">self-assessment on character strength</a>. I don’t usually go out of my way for online quizzes but this one came recommended.</p><p>The result? For me…….<strong>Curiosity</strong> <strong>is King!</strong></p><p>(FYI — my top 10 are listed below)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*hx4kbXzWHFEOqiLqRrSSGQ.jpeg" /></figure><p>This wasn’t a surprise. What was is how often I’ve referenced the results ever since. If sometimes like me you struggle to describe yourself (or explain your actions!) you should also give it a go. Self-awareness and the sharing of your strengths (and weaknesses) I’ve found to be a powerful tool!</p><p><a href="https://www.viacharacter.org/www/">Character Strengths, Character Building Experts: VIA Character</a></p><p>Curiosity is such a killer. You can never explore or find enough and there’s only so much you can do in a day. The <strong>reading</strong> of others’ quests becomes the short-cut to squeezing more in.</p><p>Over the years I’ve been very diligent at collecting my favourite reads. This was not in anticipation of publishing it, but more a manifestation of my reading style. As I trawl sources I won’t always read something in detail. I could (or should) be doing something else or am likely not in a moment when concentration is high. I’ll save it for later. If I do deep dive and it’s good, I’ll also want to save it for sharing later on.</p><p>The <a href="https://computers.tutsplus.com/tutorials/quick-tip-how-to-use-safaris-reading-list--mac-47349">Reading List</a> feature in Safari is my place for safe keeping. It’s accessible from all my different apps/sources and what you may not realise, it offers an offline capability which is perfect for flights.</p><h4>My Top Sources</h4><ol><li><a href="https://news.ycombinator.com/">Hackernews</a> — a collection of mostly, but not limited to, start-up techies. Includes Tech Trends, Current Affairs, Engineering tales. I value not just all the articles shared but the quality, diversity and depth of the commentary.</li><li>Twitter (people I know from conferences, companies relevant to my work, colleagues and industry figures). Check out my <a href="https://twitter.com/mvillis">Twitter</a> to see who I follow for some ideas. The wonderful thing about Twitter is that every time someone you follow re-tweets something, it’s possibly someone else you could follow. A great way to grow your network.</li><li><a href="http://medium.com/">Medium</a> — has over the past year become the go-to blogging platform. Its recommendation engine is really good and often shows articles from people not necessarily very well known in the industry (but have done/written some amazing things).</li></ol><h4>Launching my Reading List!</h4><blockquote><a href="https://www.mikevillis.com/reading">https://www.mikevillis.com/reading</a></blockquote><p>There are roughly 40 articles there covering DevOps, Leadership, Career, Architecture as well as some generally fascinating reads I’ve collected over the last 4 years. <strong>I would love to hear if you find any article useful or engaging. Most represent something that to me is aspirational, well-articulated or inspiring.</strong></p><p>The unexpected perk of having and sharing this list, is that it provides a rich tapestry of pointers about myself. Maybe, if like me, you have’t felt that personal self-assessments are for you (and this blog hasn’t convinced you otherwise!) this could be a great way to get to know you. The final artefact could even be much richer!</p><h4>Final Top Tips for the Curious Reader</h4><ol><li>Don’t necessarily go for traditional media. Twitter makes for a great news feed. Follow people who both inspire you or remind yourself of you. Wouldn’t want to create an echo chamber.</li><li>Be mindful that you may not always be in the right moment. Save and come back. Makes sharing later on easier too!</li><li>As per #2 — have a place — probably best to be available across difference sources/devices. Make it easy to save and find.</li><li>Remember <strong>not everyone has Curiosity as their primary character</strong> <strong>strength</strong>. This means two-fold. #1 You have an obligation to the world to share your passion for new and interesting things. #2 Don’t go over the top. There is such a thing as over sharing :-)</li></ol><h3>My Top 10 Character Strengths — FYI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UOSiEpJ4-9L5joQpArOPgA.png" /><figcaption>My top 10 character strengths according to Via Character</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=229777ffaeac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bikebytes/curiosity-is-king-and-the-launch-of-my-reading-list-229777ffaeac">Curiosity is king! And the launch of my reading list</a> was originally published in <a href="https://medium.com/bikebytes">BikeBytes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple React Site with create-react-app, Github pages, Travis CI and CloudFlare]]></title>
            <link>https://medium.com/bikebytes/simple-react-site-with-create-react-app-github-pages-travis-ci-and-cloudflare-8a859daa881?source=rss-a7c38140d775------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a859daa881</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[travis-ci]]></category>
            <category><![CDATA[cloudflare]]></category>
            <dc:creator><![CDATA[Michael Villis]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 16:17:18 GMT</pubDate>
            <atom:updated>2017-07-08T03:25:28.044Z</atom:updated>
            <content:encoded><![CDATA[<h4>The foundations of mikevillis.com</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-T2V6LWYxayGnhpmOjuc8A.png" /><figcaption>tl;dr — link all these tools together and start living the webmaster dream</figcaption></figure><p>There’s no shortage of tools and frameworks out there to help you build a web site. At one end of the spectrum are the all-in-one platforms like <a href="https://wordpress.com/">Wordpress</a> and <a href="https://www.wix.com/">Wix</a>. They’re easy to get started, include baked-in templates and offer free tiers.</p><p>What’s not to like?<strong> Why doesn’t this blog just end here?</strong></p><p>Depending on your motivation, like me, you might be willing to <em>nerd it up</em> a bit….live on the edge……discover the inner craftsman on your journey to becoming a webmaster!</p><p>The good news is you have choices. Here’s a couple I considered:</p><ul><li><a href="https://gohugo.io/">The world&#39;s fastest framework for building websites</a></li><li><a href="https://jekyllrb.com/">Jekyll * Simple, blog-aware, static sites</a></li></ul><p>For a long time, I’ve been a fan of <a href="https://pages.github.com/">Github Pages</a> as a host for simple websites. There’s something amazingly simple about HTTP enabling your code repo and minimising the number of moving pieces. Whatever framework I picked had to work with this. Most static site generators like Hugo and Jekyll work well with Github pages. As long as they produce plain, static content (something that a browser will understand without any server side processing) — it’ll work with Github pages.</p><p>Of late I’ve been building websites on <a href="https://facebook.github.io/react/">React</a> (<a href="https://www.tradepad.com.au/">https://www.tradepad.com.au</a>, <a href="https://measuremate.herokuapp.com/">https://measuremate.herokuapp.com</a>). One of the things I’ve learnt over the years is when to pick your technical battles. Knowing that content would be the biggest and most important challenge for the site, sticking with what I knew and avoiding a new framework seemed wise.</p><p>If React isn’t for you (tbh it’s fair to call it overkill for a site this simple), it’s ok to stop and make your own careful decision. The overall pattern described on this blog would work for most static site generators.</p><p>React is perfectly compatible with Github pages. In the past, I’ve relied on the unofficial but perfectly equipped <a href="https://github.com/kriasoft/react-static-boilerplate">react-static-boilerplate</a> project to get going quickly. <a href="https://github.com/facebookincubator/create-react-app">create-react-app</a> has built momentum of late as the official getting started project. I was keen to check this out and see if it’s worth switching for my other projects.</p><p>So at this point here’s how things are looking:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/1*tDVV4VP0EWJmKlKOgspf4w.png" /><figcaption>Basic setup for presenting content from Github to users</figcaption></figure><p>Github pages by default uses your github user or organisation name to provide a URL for your site. This assumes that you’ve followed the setup instructions correctly and named your repo <em>username.github.io</em>. My site URL would be <a href="http://mvillis.github.io./">http://mvillis.github.io.</a> This is not the worst URL but nothing says polished website like your own shiny domain name. There’s no shortage of companies that will let you check and register your website name. I went with <a href="https://www.crazydomains.com.au/">Crazy Domains</a> and secured <em>mikevillis.com.</em></p><p>Putting your DNS to work is <a href="https://help.github.com/articles/setting-up-an-apex-domain-and-www-subdomain/">documented pretty well</a> by Github. If like me you wanted both <a href="http://mikevillis.com/">http://mikevillis.com</a> (Apex domain) &amp; <a href="http://www.mikevillis.com/">http://www.mikevillis.com</a> (www sub domain) to resolve to the site, the following records needed to be added to DNS. This was a change inside the Crazy Domains console:</p><blockquote>CNAME =&gt; <a href="http://www.mikevillis.com/">www.mikevillis.com</a> =&gt; mvillis.github.io</blockquote><blockquote>A Record =&gt; mikevillis.com =&gt; 192.30.252.153, 192.30.252.154</blockquote><p>It’s worth noting that we can make the www record map directly to the friendly name <em>mvillis.github.io</em>. Apex records (ie. mikevillis.com) cannot be mapped to friendly names but must be mapped to IP addresses. Some DNS providers support CNAME flattening which is a way to fake support for CNAMEs on apex domains. Use this if you can.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Fjo3mRmt6fUMOvOTQDoow.png" /></figure><p>To get things working you now just need to update the settings of your Github repository to turn on Github Pages and update the custom domain to match your website.</p><p>If you had any content in your repo, it would now be accessible via your site DNS.</p><h3>There’s more</h3><p>At this time I thought I was pretty much done however there were two key issues that still needed solving:</p><p><strong>(1)</strong> How to manage the process of generating the final static content from the React Source code (or whatever your chosen framework is)? What triggers it? Where is the output placed? How do we ensure that it doesn’t influence the site URL. ie. we don’t want the site to be accessible from www.mikevillis.com/build? It must just be the root of the site. How can we ensure changes aren’t made live if any quality checks fail (ie. pre-merge)? We’ll call these collectively <strong>Build/Deploy</strong> issues.</p><p><strong>(2)</strong> Github pages don’t support <strong>HTTPS</strong> for custom domain names. This makes sense. They don’t have the ability to generate a valid certificate and they don’t allow you to supply one.</p><h4>Build / Deploy</h4><p>For many reasons, even though a React project is just javascript/html, production ready artefacts look very different to source code. By default, <em>create-react-app</em> provides the <em>$yarn build</em> command to generate these artefacts and places them in a folder called <em>build</em>. Running this command locally, checking in this <em>build</em> folder to Github and pointing Github Pages to the <em>build</em> folder as the location to serve to the web would be the simplest option to resolving this issue.</p><p>This is almost supported! Github does allow you to <a href="https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/#publishing-your-github-pages-site-from-a-docs-folder-on-your-master-branch">configure a page source</a>. This could be another branch or a hard-coded folder but only if it’s called <em>docs</em>. We could hack the build script to write to a folder called <em>docs </em>instead of build and <strong>Boom!! </strong>Job done.</p><p>Not quite. Unfortunately, this <em>docs</em> folder option is not available for root projects (ie. username.github.io). Only for child ones (eg. username.github.io/preso). Ugh.</p><p>To solve this problem I needed to orchestrate a process to run the build script and then place the output to a separate location. This location could either be a separate branch or a repository separate from the source code. I’m not a fan of maintaining multiple branches in a single repository that will never merge. For this reason, I opted to create a completely separate repo for the production-ready build artefacts.</p><p><a href="https://travis-ci.org/">Travis CI</a> is simple CI tool which for Public Github Projects (like mine) is totally <strong>free</strong>. We can configure it to listen for code changes in our Github repo, build the app (including running any tests), and, should everything pass, push the production artefacts to our separate repository. This is made even easier by Travis CI’s Github Pages integration:</p><p><a href="https://docs.travis-ci.com/user/deployment/pages/">GitHub Pages Deployment - Travis CI</a></p><p>Travis CI is driven by a codified pipeline expressed as a YAML file in your source code repository. You can explore my pipeline code in Github for reference. Look for the <em>test, build, deploy </em>steps<em>.</em></p><p><a href="https://github.com/mvillis/src.mvillis.github.io/blob/master/.travis.yml">mvillis/src.mvillis.github.io</a></p><p>The end to end process is now looking a bit more complicated with the addition of this second repository and Travis CI to orchestrate its populated. There’s just one last piece — CloudFlare. Let’s get to it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-T2V6LWYxayGnhpmOjuc8A.png" /></figure><h4>HTTPS</h4><p>You might consider HTTPS a nice to have. This site after all will not contain any sensitive content. There are other good reasons to implement HTTPS including <a href="http://www.httpvshttps.com/">HTTP2 performance benefits</a> and search engine optimisations.</p><p>I spend a lot of my time in my professional life talking about security. This is definitely one of those moments to lead by example!</p><p>There are many CDN / WAF / DDoS solutions out there that provide HTTPS for backend websites. What makes CloudFlare special however is their <strong>FREE</strong> tier!</p><p>Troy Hunt has an <a href="https://www.troyhunt.com/how-to-get-your-ssl-for-free-on-shared/">excellent blog on setting up your website</a> (in his case it was an Azure hosted service but the same applies to Github pages). The steps can be summarised as:</p><ul><li>Transferring your DNS setup to CloudFlare (done in CloudFlare)</li><li>Pointing your Name Servers across to CloudFlare (done for me in Crazy Domains)</li><li>Adding a page rule to redirect any HTTP connections</li></ul><blockquote><strong>Fun Fact </strong>— when you configure Github Pages to use your custom domain it stops anyone from going straight to <em>username.github.io</em> and will always enforce a redirect.</blockquote><p>Now it’s time for you to prove me wrong. See if it works!. Try going to:</p><ul><li><a href="http://mikevillis.com/">http://mikevillis.com</a></li><li><a href="http://mvillis.github.io/">http://mvillis.github.io</a></li></ul><p>:-)</p><h4>Final Words</h4><p>With all this combined I was able to provide a React based site that is serverless, free, secure, fast and has a known process for releasing changes. Keen to hear if this is helpful to you, other approaches or articles in this space and any other feedback.</p><h4>— Update (2017–07–08) Github pages and React Routing —</h4><p>Single Page Application (SPA) frameworks like React use libraries such as react-router to update site content in line with user navigation; keeping the browser URI in sync as you go and avoiding full page reloads. This is done mostly using <em>pushState</em> and the <em>HTML5 History API.</em></p><p>This all sounds pretty good but unfortunately it brings one issue for our site. All the app content is linked to the site root (ie. <em>index.html). </em>If you reload on any other URI (eg. <em>&lt;root&gt;/sub-page</em>) you’ll get a nice <em>404 Not Found</em> error and your router won’t have a chance to show anything.</p><p>If you’re using HTTP hosting options like <a href="http://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html">s3 Websites</a> or <a href="https://surge.sh/">Surge.sh</a> they provide configurations to redirect your site to your Root content (while maintaining the correct navigation URI).</p><p>Github Pages doesn’t provide a redirect capability. It does however allow you to <a href="https://help.github.com/articles/creating-a-custom-404-page-for-your-github-pages-site/">customise the content that is displayed when a 404 is triggered</a>. This allows for some crafty hackery courtesy of this Github repo:</p><p><a href="https://github.com/rafrex/spa-github-pages">rafrex/spa-github-pages</a></p><p>Via some javascript in your 404.html file, you can trigger a redirect to the root of your website with the original path as a query string.</p><blockquote>eg. <a href="https://www.mikevillis.com/reading">https://www.mikevillis.com/reading</a> <strong><em>becomes</em></strong> <a href="https://www.mikevillis.com/?p=/reading">https://www.mikevillis.com/?p=/reading</a></blockquote><p>Some extra code in <em>index.html</em> will intercept the request, convert it back into the correct url and add it to the browser’s history using <em>window.history.replaceState</em>. This doesn’t trigger the browser to attempt to load the new url but does allow react-router to process the correct url and route accordingly.</p><p>Check out my implementation =&gt; <a href="https://github.com/mvillis/src.mvillis.github.io/blob/master/public/404.html">404.html</a> &amp; <a href="https://github.com/mvillis/src.mvillis.github.io/blob/master/public/index.html">index.html</a></p><p>Problem solved. Happy days!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a859daa881" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bikebytes/simple-react-site-with-create-react-app-github-pages-travis-ci-and-cloudflare-8a859daa881">Simple React Site with create-react-app, Github pages, Travis CI and CloudFlare</a> was originally published in <a href="https://medium.com/bikebytes">BikeBytes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Launch]]></title>
            <link>https://medium.com/bikebytes/launch-55583c4df741?source=rss-a7c38140d775------2</link>
            <guid isPermaLink="false">https://medium.com/p/55583c4df741</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[launch]]></category>
            <category><![CDATA[learn]]></category>
            <dc:creator><![CDATA[Michael Villis]]></dc:creator>
            <pubDate>Mon, 12 Jun 2017 13:33:30 GMT</pubDate>
            <atom:updated>2017-06-12T13:33:30.421Z</atom:updated>
            <content:encoded><![CDATA[<h4>First blog. Let’s go!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aqTf4HWplcRFEUCD_ilplQ.jpeg" /><figcaption><a href="https://unsplash.com/search/launch?photo=-p-KCm6xB9I">https://unsplash.com/search/launch?photo=-p-KCm6xB9I</a></figcaption></figure><p>I’ve been sitting on <a href="https://www.mikevillis.com/">mikevillis.com</a> for almost 12 months now. At the time of registering, I was convinced that I had something worth sharing and naturally worthy of my own internet presence.</p><p>I still think this is true.</p><p>Altruism (and modesty) aside, I’ve come to appreciate that documenting my adventures is possibly <strong>more about taking the time to reflect</strong> <strong>than necessarily changing the world</strong> (though this is still a meaningful bonus to me).</p><p>Time always seems to be more scarce than good intentions so we’ll see how this one goes. Mark 12th June in your calendars. Let’s start this 12-month experiment and see how it goes!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55583c4df741" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bikebytes/launch-55583c4df741">Launch</a> was originally published in <a href="https://medium.com/bikebytes">BikeBytes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>