<?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 Elmer Bulthuis on Medium]]></title>
        <description><![CDATA[Stories by Elmer Bulthuis on Medium]]></description>
        <link>https://medium.com/@elmerbulthuis?source=rss-87859060c8e3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*JSXhPv_jZlzA_UCd.</url>
            <title>Stories by Elmer Bulthuis on Medium</title>
            <link>https://medium.com/@elmerbulthuis?source=rss-87859060c8e3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:08:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@elmerbulthuis/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[v0.0.0-local]]></title>
            <link>https://medium.com/@elmerbulthuis/v0-0-0-local-9c3a89999cd?source=rss-87859060c8e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c3a89999cd</guid>
            <category><![CDATA[versioning]]></category>
            <category><![CDATA[continuous-deployment]]></category>
            <category><![CDATA[development-environment]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Elmer Bulthuis]]></dc:creator>
            <pubDate>Thu, 21 May 2020 10:35:40 GMT</pubDate>
            <atom:updated>2020-05-21T10:35:40.387Z</atom:updated>
            <content:encoded><![CDATA[<p>When developing a piece of software, it’s actually version-less! The software should acquire a version only when it is released. At Gameye, releasing a piece of software basically means tagging it in git with a v… tag. The git tag will be read by our CI system that will then publish that piece of software with the right version.</p><p>Having the git tag to be leading has a lot of advantages. We have a single workflow for releasing anything that has git. And there is a UI for it in GitHub that our release managers like. Also we can be sure that anything that we release always has one version that is consistent with the git tag.</p><p>A lot of programming languages have a version field somewhere in their environment. Node.js has the version field in package.json, Rust has a version field in it’s Cargo.toml file, there is also a version field present in openapi.yaml that we like to use to describe our api’s.</p><p>These version fields usually are not allowed to be empty, so we need to always set a version. But when we develop, what version do we put there? Software should only have a version when it is released and not in between. Also we have the git tags that are leading! Problem!</p><p>That is why we use the 0.0.0-local version. We use this version for all unreleased, version-less software.</p><p>The 0.0.0 indicates that there is no version. 0 is the closest thing to nothing that we have with numbers, and we have three of those 0’s here. This should feel as if it is a synonym to no-version.</p><p>According to the semver standard (that we love) the -local indicates a prerelease that is called “local”. This is kind of how we use this version. When developing this software we might link is to another piece of software for local testing. So in that case it is used as a prerelease.</p><p>In CI we can always set the version by simple cutting of the first v in the git tag and replacing 0.0.0-local with the actual version. In some languages we can use a more luxurious approach than find-and-replace. In Node.js we can do a npm version 1.2.3, in Go we can set the version during build (via -ldflags). If we do not have this luxury we can always resort to the find-and-replace.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c3a89999cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using medium as a backend for our blog.]]></title>
            <link>https://medium.com/gameye/using-medium-as-a-backend-for-our-blog-5e70737f0610?source=rss-87859060c8e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e70737f0610</guid>
            <category><![CDATA[nginx]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[cors]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Elmer Bulthuis]]></dc:creator>
            <pubDate>Fri, 25 Oct 2019 11:22:00 GMT</pubDate>
            <atom:updated>2019-11-14T20:32:33.555Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wP8KjElQ1QH0i62uTNMQdA.png" /></figure><p>So we, as many companies, want to have a blog. We use this as a marketing tool for both our developers and clients. Medium seemed the right choice, since they are kind of the standard for blogging and offer some nice features.</p><p>But we also want to integrate our blog in our website. At least in the design of our website.</p><p>With medium you can design your publication page a bit, but this was nog enough for us. We want to have complete control of how our blog looks and feels.</p><p>So we looked into the ?format=json option in medium. Add this to your log url and you get the content of the blog as json. Ideal for including that content in your own website!</p><p>But we wanted even more. We wanted a client side only solution so we wouldn’r have to write a backend. Now we cannot get the json from medium in our browser because of CORS headers.</p><p>We came up with very simple solution that is basically a proxy that adds the neccessary headers. We do this via NGINX, by using the following configuration:</p><pre>server {<br>    listen 80 default_server;</pre><pre>    location / {<br>        add_header Access-Control-Allow-Origin &quot;*&quot;;<br> <br>        proxy_set_header Origin &quot;&quot;;<br>        proxy_pass <a href="http://medium.gameye.com/gameye/">http://medium.gameye.com/gameye/</a>;<br>    }<br>}</pre><p>And now we can use the blog-content directly from our client-side applications.</p><p>Or, well, the json that you get from medium is actually a bit flaky, it starts with some rubbish. For some reason the json is prefixed with some javascript and an x closing tag, so we cut off everything before the first {. Our code for reading the blog posts looks something like this:</p><pre>async function fetchBlogData(blogName) {<br>    const response = await fetch(&quot;<a href="http://54.194.25.241/test-blog-25b6cdca4a13?format=json">http://blog.gameye.com/&quot; + blogName + &quot;?format=json</a>&quot;);<br>    const textData = await response.text();<br>    const data = JSON.parse(textData.substring(textData.indexOf(&quot;{&quot;)));</pre><pre>return data;<br>}</pre><p>happy blog-integrating! :-)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e70737f0610" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gameye/using-medium-as-a-backend-for-our-blog-5e70737f0610">Using medium as a backend for our blog.</a> was originally published in <a href="https://medium.com/gameye">Gameye</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This is Puk, she’s great!]]></title>
            <link>https://medium.com/@elmerbulthuis/this-is-puk-shes-great-6ac8968fd460?source=rss-87859060c8e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ac8968fd460</guid>
            <dc:creator><![CDATA[Elmer Bulthuis]]></dc:creator>
            <pubDate>Fri, 25 Oct 2019 11:06:43 GMT</pubDate>
            <atom:updated>2019-10-25T11:06:43.078Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Puk" src="https://cdn-images-1.medium.com/max/774/1*zn7VR-hPIH_l31N7Khg2Aw.jpeg" /></figure><p>This is Puk, she’s great!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ac8968fd460" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Carl Cox is a great DJ]]></title>
            <link>https://medium.com/@elmerbulthuis/carl-cox-is-a-great-dj-f6f046fc06c8?source=rss-87859060c8e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6f046fc06c8</guid>
            <dc:creator><![CDATA[Elmer Bulthuis]]></dc:creator>
            <pubDate>Fri, 25 Oct 2019 11:04:30 GMT</pubDate>
            <atom:updated>2019-10-25T11:04:30.333Z</atom:updated>
            <content:encoded><![CDATA[<p>He’s been around for a very long time. Always delivering his signature sound that never really goes out of style.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZdAwiV4T22I%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZdAwiV4T22I&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZdAwiV4T22I%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ba169b5eb690d11f0f5fa176b66f5b46/href">https://medium.com/media/ba169b5eb690d11f0f5fa176b66f5b46/href</a></iframe><p>Here we see him playing for Cercle, a french thing where they let DJ’s play at beautiful locations while makeing a video of it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6f046fc06c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>