<?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 thefoxdiaries on Medium]]></title>
        <description><![CDATA[Stories by thefoxdiaries on Medium]]></description>
        <link>https://medium.com/@foxietamine?source=rss-115c11394ba2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1BZLMUfLvAXd0T0u0FCdjg@2x.jpeg</url>
            <title>Stories by thefoxdiaries on Medium</title>
            <link>https://medium.com/@foxietamine?source=rss-115c11394ba2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:32:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@foxietamine/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[How to build The Best Plex Server: Hardware (Part 1)]]></title>
            <link>https://medium.com/@foxietamine/how-to-build-the-best-plex-server-hardware-part-1-b4c6bbcf6aed?source=rss-115c11394ba2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4c6bbcf6aed</guid>
            <category><![CDATA[servers]]></category>
            <category><![CDATA[plex]]></category>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[medium]]></category>
            <dc:creator><![CDATA[thefoxdiaries]]></dc:creator>
            <pubDate>Sun, 26 May 2024 15:06:50 GMT</pubDate>
            <atom:updated>2024-05-26T15:11:09.602Z</atom:updated>
            <content:encoded><![CDATA[<p>Learn how to build a relatively cheap custom Plex Server with the best hardware (CPU &amp; GPU) for streaming and transcoding.</p><p>This is part 1 of a 3 part series dedicated to building a home multimedia heaven centered around Plex.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tA8Hw9qDBhOQ0w3P" /><figcaption>Photo by <a href="https://unsplash.com/@gabimedia?utm_source=medium&amp;utm_medium=referral">Gabriel Vasiliu</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Opening Statement</h3><p>I’m a <em>problem solver</em>. When I have a problem <em>(or at least when I think I have one)</em>, I try to find a proper solution to it, therefore I end up doing a lot of <strong><em>investigation</em></strong>. The problem I faced not-so-long-ago was that I was running, probably as you are, my Plex Server on my gaming PC and there were, let’s say, a few downsides to it:</p><ul><li>the PC had to stay always on, which in its turn ends up consuming lots of power <em>(and can also slowly start degrading components)</em></li><li>gaming sessions or video editing on the same PC would be a bit downgraded when some transcoding or library scanning or media downloading was also happening on Plex’s side, since they were sharing the same resources</li><li>I had a system centered around AMD, which is not that great at transcoding (yet)</li><li>kindof expensive build for just running Plex <em>(if I were just to run Plex on it)</em></li></ul><p>This, plus the fact that thinking about something new to build got my dopamine levels startled, made me begin my journey towards finding <strong>the best hardware for building a dedicated server</strong> which I’d use for my home <strong>multimedia heaven</strong>.</p><p>My main concerns were <strong>performance</strong> — this server should be able to handle multiple video streams and transcoding’s as best as possible — and <strong>performance-to-power-consumption ration</strong>, as well as for it to be small <em>(aesthetic preference — I had an idea and wanted it to fit in a shelf in a library, as I thought it would looks pretty cool [and it does!]).</em> Ah, aand also: to not cost a fortune!</p><p>While doing my research, one of my first guide I ended up basing the rest of the search for components on was <a href="https://www.reddit.com/r/PleX/comments/13yeh5r/lets_have_a_talk_guide_to_choosing_the_best_plex/">this reddit post</a>, which is pretty comprehensive in explaining some basic Plex concepts and requirements, which I will not bother doing here again <em>(if you are not that familiar with the differences between direct play / transcoding or CPU/GPU video decoding or general more in-depth Plex knowledge, I recommend you to read it)</em>.</p><h3>Shopping //Components</h3><p>A comprehensive list of all the components you need to buy.</p><h4><strong>1. Intel NUC</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*i5m5hlHZ-CDe3MdY.jpg" /></figure><p>This will be the core of the setup. NUCs are powerful Mini-PCs which have a key component: an <strong>Intel Processor</strong> with an <strong>iGPU</strong> which supports <strong>QuickSync</strong> <em>(usually identified as Intel Iris Xe Graphics).</em> This is very important, because this is the very epicenter of video processing and transcoding.</p><blockquote>💡 Dedicated GPUs like NVidia can be more powerful in this area, but usually that power does not help that much in these particular video processing scenarios and the Intel iGPUs have the advantage of having more streams (aka more videos processed in parallel).</blockquote><p>My recommendation here is the <a href="https://www.asus.com/displays-desktops/nucs/nuc-mini-pcs/asus-nuc-13-pro/techspec/"><strong>ASUS NUC 13 Pro Kit</strong></a> — version <strong>NUC13ANKi5</strong> with an <a href="https://www.intel.com/content/www/us/en/products/sku/232126/intel-core-i51340p-processor-12m-cache-up-to-4-60-ghz/specifications.html"><strong>i5–1340p 13th generation processor</strong></a> and <strong>no RAM</strong>, <strong>no storage</strong>, <strong>no OS</strong>, and, in some variants, <em>no power cord</em>.</p><p>This is the perfect choice, because it has a relatively recent generation of processors which supports major codecs <em>(x264, x265, even AV1)</em> <strong>blazingly fast</strong>.</p><p>You can also try the <a href="https://www.asus.com/displays-desktops/nucs/nuc-kits/asus-nuc-12-pro/"><em>12th generation version</em></a>, or the newer <a href="https://www.asus.com/displays-desktops/nucs/nuc-mini-pcs/asus-nuc-14-pro/"><em>14th generation</em></a>, depending on your budget, but I found this to be the most balanced.</p><p>Search for it at your favorite retailer — I bought mine for around <strong>520 EUR</strong> (560 USD).</p><h4><strong>2. AC Power Cord (optional)</strong></h4><p>For some versions of the NUC kit, you can find it doesn’t come with a power cord, only with a power adapter — <strong>C5</strong> type (see <a href="https://www.asus.com/me-en/support/faq/1052533/">here</a> in their specs). So you can <a href="https://www.amazon.com/c5-power-cord/s?k=c5+power+cord"><strong>buy one</strong></a> separately — they are pretty cheap <em>(or you might already have one lying around at home)</em>, or you can opt to get the kit with the power cord included.</p><p>The price is usually around <strong>5–10 EUR</strong>/USD.</p><h4><strong>3. SODIMM Dual-Channel RAM</strong></h4><p>The NUCs are small. Really small. Almost as small as a book <em>(and pretty, and silent)</em>. But, because they are so small, they require small components — that includes the memory. That’s why it needs a notebook memory — <strong>SODIMM</strong> type. Be careful not to buy <em>(or hope to use)</em> normal PC memory as it won’t fit / work.</p><p>Also an important aspect — the GPU within the processor is, quote, <em>“Intel Iris XE eligible”</em>, which basically translates into <em>“it works at full capacity if you have dual-channel memory”</em>. So make sure to get a dual-channel memory kit.</p><p>I use <a href="https://www.corsair.com/uk/en/p/memory/cmsx16gx4m2a3200c22/vengeancea-series-16gb-2-x-8gb-ddr4-sodimm-3200mhz-cl22-memory-kit-cmsx16gx4m2a3200c22"><strong>Corsair’s VENGEANCE 16GB (2 x 8GB) DDR4 SODIMM 3200MHz CL22 Dual-Channel Kit</strong></a>. It’s about <em>50 EUR / 55 USD</em>.</p><p>I found mine at a discount at <strong>35 EUR</strong>.</p><h4><strong>4. NVME M2 Storage</strong></h4><p>I know that you most likely already have some massive HDDs for storing your movies and tv-shows, but it is unadvisable to use those for storing the operating system of the server you’re about to build. And, because, remember, the NUC is <em>really-really small</em>, it is also picky on what internal storage it can use. So if you already have some NVME M2 small SSD at home, that’s great, you can reuse it, bit if not, you need to buy one.</p><p>My choice was an <a href="https://www.amazon.de/-/en/SAMSUNG-PM991-MZVLQ256HBJD-256GB-Internal/dp/B0BC25B3TV"><strong>SAMSUNG PM991 256GB M.2 22x80 PCIe NVMe SSD</strong></a> which I bought for <strong>24 EUR</strong> / 26 USD. You can go with lower versions (e.g. 128GB) something similar to your choice, but be careful about the form factor (NVME + M2).</p><h4><strong>5. 4, 3, 2, 1 HDDs?</strong></h4><p>I suppose you already have some nice HDDs where you keep your multimedia files on. But if you don’t, you obviously need to buy one.. or two.. or more. I’ll leave this up to your preferences. Just make sure they have a great cache and best speeds <em>(7200RPM)</em>.</p><p>I already had some, so I spent no money on this chapter <em>(I use Seagate’s HDDs, Ironwolf and such)</em>.</p><h4><strong>6. HDD Rack or Direct Access Storage (DAS) Solutions</strong></h4><p>Probably the most precious part of your setup — connecting your HDDs to the system. All of this will be done externally, through the many USB and Thunderbolt ports that this NUC provides <em>(3 USB 3.2 and 2 Thunderbolt-USBC ports).</em> Depending on how many HDDs you have, you have two options:</p><ol><li>A simple <strong>3.5’’ HDD Rack</strong> — a lot cheaper, it’s usually one per hard-disk, so you can by up to maximum the number of ports you have, which is 5</li><li>A more complex <strong>DAS</strong> Solution, like <strong>RAID Storage Kits</strong> — these are more expensive, but have a single connection and can usually support lots of HDDs</li></ol><p>Some examples of HDD simple Racks can be found <a href="https://eu.ugreen.com/collections/for-laptop/products/ugreen-usb-to-sata-adapter-sata-to-usb-3-0-cable-hard-drive-adapter-sata-i-ii-iii-hard-drive-reader-compatible-with-3-5-2-5-hdd-ssd-laptop-raspberry-pi-4-crucial-wd-seagate-toshiba">here</a> or <a href="https://eu.ugreen.com/collections/for-laptop/products/ugreen-6-in-1-usb-to-sata-or-ide-adapter?variant=40296225538131">here</a>. You can go with your favorite if you want it to have an enclosure or other fancy stuff <em>(I enclosed mine in some cases I already owned)</em>.</p><p>I bought just one of these, as at the moment I have a single giant HDD for around <strong>10 EUR/USD</strong>.</p><p>If you want to go with a more advanced DAS solution, get ready to pump that cash — some good examples are the <a href="https://www.terra-master.com/global/d5-300c.html">TerraMaster D5–300C</a> or <a href="https://www.vexio.ro/network-attached-storage/qnap/338137-tr-004-usb-3-0-type-c/?gad_source=1&amp;gclid=Cj0KCQjw_-GxBhC1ARIsADGgDjs9cQWd5KlxNcxISctiKnKRf5dONxTKmlnEyQzy2PIQ9Ocr80t53FEaAlMFEALw_wcB">QNAP TR-004</a>, both of which cost about <strong>230 EUR</strong> / 240 USD. I think these are worth investing after you gather too many HDDs, otherwise — not worth it.</p><p><strong>The most important thing to keep in mind</strong> for both of the options: <strong>make sure that they have either no power button or the manufacturer specifies that they can automatically power-on when power is lost.</strong> This is going to be an always-running server, so it’s of utmost important that the HDD starts automatically back up after power returns.</p><h4><strong>7. Accessories</strong></h4><p>You want to make sure to connect your hardware <em>directly to the Internet</em> (well, not literally), therefore use a high speed cable, don’t connect it through Wi-fi.</p><p>I had to buy one such cable — so if you need one too, get yourself an <strong>UTP CAT6 RJ45 network cable</strong> <em>(asses the length you need based on where you want to store your hardware and where’s your router)</em>.</p><p>You might also need an <strong>extension cord</strong> — I definitely needed one as I didn’t have an electrical outlet close-by the place I was going to mount it.</p><p>I bought each of these items for around <strong>10 EUR</strong> / USD each.</p><h4><strong>8. Accessories V2</strong></h4><p>This is not something that you need to buy, but something you need to make sure you have <em>(even if it’s obvious you need to)</em>: in order to connect to the system and install it, configure it etc. you need to own:</p><ul><li>a keyboard and a mouse</li><li>a monitor / screen (with HDMI cable)</li><li>an USB drive or similar where you can create a bootable version of Ubuntu (or your favorite linux distro)</li></ul><p>All of these are required only for the setup step, afterwards they are absolutely not needed anymore, so you can reuse those from your PC.</p><h3>Putting the components together</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q12Ojz101Gj2Kgyp" /><figcaption>Photo by <a href="https://unsplash.com/@christianw?utm_source=medium&amp;utm_medium=referral">Christian Wiediger</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I will not bother with telling you how to connect a mouse or a monitor to the NUC or how to plugin the internet cable.</p><p>But you should know that for setting up the RAM and internal SSD you need to open-up the NUC by unscrewing the back — when you do that you get access directly to the slots for the dual-channel RAM kit and for the M2 SSD <em>(if you have trouble you can also google it)</em>. Mount them, enclose the NUC back and that’s it.</p><h3>Epilogue</h3><p>If we add together all the components that I purchased in order to get this setup, it’s around:</p><pre>| Item           | Price (EUR)<br>| ---            | --- <br>| NUC            | 520 <br>| AC Power Cord  | 5 <br>| RAM            | 35 <br>| SSD            | 24 <br>| HDD Rack       | 10 <br>| UTP cable      | 10 <br>| Extension cord | 10 <br>| TOTAL          | 614 </pre><p>So a total of approximately <strong>620 EUR</strong> / 670 USD.</p><p>Now that you’ve spent the money and you connected everything together, you’re finally done — you can press the power button!</p><p><em>PS: You won’t see anything yet tho’, since you don’t have anything installed on it. Part 2 of this tutorial is going to help you to properly configure your server to work like an autonomous multimedia spaceship that it strives to be.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4c6bbcf6aed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dune: Part Two is God’s second coming, in cinema form]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@foxietamine/dune-part-two-is-gods-second-coming-in-cinema-form-1432b27df0fb?source=rss-115c11394ba2------2"><img src="https://cdn-images-1.medium.com/max/800/1*MbWlGJUU3DYYz1nlWh09OA.jpeg" width="800"></a></p><p class="medium-feed-snippet">Paul Atreides. Kwisatz Haderach. Lisan al Gaib. Messiah. Muad&#x2019;Dib. A true character.</p><p class="medium-feed-link"><a href="https://medium.com/@foxietamine/dune-part-two-is-gods-second-coming-in-cinema-form-1432b27df0fb?source=rss-115c11394ba2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@foxietamine/dune-part-two-is-gods-second-coming-in-cinema-form-1432b27df0fb?source=rss-115c11394ba2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1432b27df0fb</guid>
            <category><![CDATA[review]]></category>
            <category><![CDATA[movies]]></category>
            <category><![CDATA[cinema]]></category>
            <category><![CDATA[science-fiction]]></category>
            <category><![CDATA[dune]]></category>
            <dc:creator><![CDATA[thefoxdiaries]]></dc:creator>
            <pubDate>Sun, 10 Mar 2024 16:44:44 GMT</pubDate>
            <atom:updated>2024-03-10T16:44:44.982Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[A word of praise for Dune by Frank Herbert, a book every human should strive to read]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@foxietamine/a-word-of-praise-for-dune-by-frank-herbert-a-book-every-human-should-strive-to-read-b6ff87b56d44?source=rss-115c11394ba2------2"><img src="https://cdn-images-1.medium.com/max/600/1*3tsb2K7N5UR_9hkeSh_heQ.jpeg" width="600"></a></p><p class="medium-feed-snippet">Dune&#x2019;s main advantage and its pivotal role in literature is to be perfectly timeless: entire generations of humans can and will read it&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@foxietamine/a-word-of-praise-for-dune-by-frank-herbert-a-book-every-human-should-strive-to-read-b6ff87b56d44?source=rss-115c11394ba2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@foxietamine/a-word-of-praise-for-dune-by-frank-herbert-a-book-every-human-should-strive-to-read-b6ff87b56d44?source=rss-115c11394ba2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6ff87b56d44</guid>
            <category><![CDATA[essay]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[dune]]></category>
            <category><![CDATA[science-fiction]]></category>
            <category><![CDATA[literature]]></category>
            <dc:creator><![CDATA[thefoxdiaries]]></dc:creator>
            <pubDate>Thu, 07 Mar 2024 19:11:00 GMT</pubDate>
            <atom:updated>2024-03-07T19:11:00.183Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[True Detective Season 4 reinvents itself — but why?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@foxietamine/true-detective-reinvents-itself-with-season-4-but-why-69daf7b9bc2c?source=rss-115c11394ba2------2"><img src="https://cdn-images-1.medium.com/max/600/0*WiEe6L7NPGlC7UVX" width="600"></a></p><p class="medium-feed-snippet">When the long winter night comes in Ennis, True Detective takes showcasing lessons from Disney+&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@foxietamine/true-detective-reinvents-itself-with-season-4-but-why-69daf7b9bc2c?source=rss-115c11394ba2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@foxietamine/true-detective-reinvents-itself-with-season-4-but-why-69daf7b9bc2c?source=rss-115c11394ba2------2</link>
            <guid isPermaLink="false">https://medium.com/p/69daf7b9bc2c</guid>
            <category><![CDATA[review]]></category>
            <category><![CDATA[cinema]]></category>
            <category><![CDATA[woke]]></category>
            <category><![CDATA[tv-shows]]></category>
            <category><![CDATA[tv-series]]></category>
            <dc:creator><![CDATA[thefoxdiaries]]></dc:creator>
            <pubDate>Mon, 05 Feb 2024 19:56:53 GMT</pubDate>
            <atom:updated>2024-02-12T12:42:59.837Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to publish your React Application under a Docker container]]></title>
            <link>https://medium.com/@foxietamine/how-to-publish-your-react-application-under-a-docker-container-23ec186f0fdb?source=rss-115c11394ba2------2</link>
            <guid isPermaLink="false">https://medium.com/p/23ec186f0fdb</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[thefoxdiaries]]></dc:creator>
            <pubDate>Sat, 27 Jan 2024 15:14:30 GMT</pubDate>
            <atom:updated>2024-02-21T13:57:00.355Z</atom:updated>
            <content:encoded><![CDATA[<p>customizable setup, configuration, nginx and Docker — explained</p><p>So, you want to build yourself a nice, standardized, containerized React web application, running under the latest and fanciest <a href="https://docs.docker.com/">Docker </a>infrastructure, but you don’t know exactly how to grasp it, and the solution and explanations around the web elude you?</p><p>Well, I’ll try to explain how it’s done, in relatively simple terms, as a concept, exemplifying the most basic, but highly configurable way of doing it, since going basic usually means also properly understanding the inner works of how and why it behaves like that <em>(so in simple terms, if you want to </em><strong><em>do it</em></strong><em> but also </em><strong><em>understand it</em></strong><em>)</em>. There are quicker ways of doing it that you can find around the web that might just work but it’s ideal that you first understand the roots / the problem, and then come up with more elegant solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FlMPAvrCoNa817C20JL6Rg.png" /><figcaption>docker + react + nginx</figcaption></figure><h3>The Problem</h3><p><a href="https://react.dev/">React </a>applications are <em>not applications by themselves</em>. Meaning you actually design or create them <em>(or both)</em>, but they don’t run out of the box, independently, like some other applications do <em>(tho’ that is debatable, since most of them don’t either, and need some application installed first, but anyways)</em>. They need a <strong>server</strong> that, by the sound of the name itself, is able to <em>serve them</em>. And since they are web applications, and after you build them they end up with a main index.html file and all the associated resources around it, any server capable of serving <a href="https://www.cloudflare.com/learning/ddos/glossary/hypertext-transfer-protocol-http/#:~:text=The%20Hypertext%20Transfer%20Protocol%20(HTTP,of%20the%20network%20protocol%20stack.">HTTP </a>requests can therefore do the job.</p><p>Then, containerizing applications usually means building <strong><em>standard flows</em></strong> around them that are able to kickstart them from source code up to happy and running, no matter the environment where that container actually runs <em>(being it your PC, your company’s cloud or AWS)</em>. Building this flow is usually done through a set of instructions in a <em>Dockerfile </em>(but more on that later). And doing that for a React application means finding means to automate the whole process of installing Node.js, the npm modules, building the application, and then running it under a server (as mentioned in the previous paragraph). One could also automate the process of cloning it, but that is an external process, and should not be part of a <strong>docker image</strong>.</p><p>For this tutorial it is important that you are familiar with the concepts of <a href="https://aws.amazon.com/compare/the-difference-between-docker-images-and-containers/#:~:text=A%20Docker%20container%20is%20a%20self%2Dcontained%2C%20runnable%20software%20application,containers%20over%20an%20application%27s%20lifecycle.">docker image and docker container</a>.</p><h3>The Solution (theoretical)</h3><p>So, in order to solve the problem, what we’ll need is:</p><ul><li>an environment running Docker <em>(locally or on a server, if you plan to automate it or deploy it etc.). </em>I’ll use a local environment for convenience, since adding intermediate infrastructure adds some complexity to the things, and I strictly want to explain the specific process, not the infra. <em><br></em>Locally you can either use<a href="https://www.docker.com/products/docker-desktop/"> Docker Desktop</a> — which is paid, or <a href="https://rancherdesktop.io/">Rancher Desktop </a>(free — check <a href="https://medium.com/obsesiicreative/how-to-migrate-from-docker-desktop-to-rancher-desktop-832253cd55c5">migration guide</a>), or <a href="https://kubernetes.io/">Kubernetes </a>or whichever is your favorite</li><li>your React application code repository, cloned locally <em>(obviously)</em></li><li>knowing the Node.js version compatible with your application <em>(in this guide we’ll use LTS, but it can be changed easily)</em></li><li>deciding on what web server to use — for the sake of simplicity and compatibility, I’ll make that decision for you <em>(isn’t it easier when somebody else makes the decisions for ourselves?)</em>, and we’ll use <a href="https://www.nginx.com/">nginx</a>, which is amongst the more common ones</li><li>finding a way to automate the installation of Node.js and the Node modules</li><li>finding a way to configure the <em>nginx </em>server to serve the application automatically</li><li>writing everything down in a <em>Dockerfile </em>with the instructions to build the image for the application <em>(this is the most important part and what is going to be the main output of this article)</em></li></ul><h3>The Solution (practical)</h3><p>We’ll have to create a file named Dockerfile in the root of your project. This will represent our <strong>image <em>source code </em></strong>that we can <strong>build </strong>and then <strong>run </strong>as a <strong>container</strong>. Your folder structure should look something like this <em>(if it doesn’t, you will need to adapt the paths from the Dockerfile in the next steps)</em>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/266/1*NRgs3LZvOV1WltAEEQ5Wag.png" /><figcaption>a new Dockerfile arrives</figcaption></figure><p>Usually, when starting defining a <strong>docker image</strong>, we need to start from a <strong>base image</strong><em> (there are plenty of base images for any of your future needs at </em><a href="https://hub.docker.com/"><em>Docker Hub</em></a><em>)</em>. Remember that docker containers are nothing else but very stripped-down <strong><em>linux virtual machines</em></strong>. And we don’t really need <em>(or want)</em> anything extra on our container <em>(as a general rule of thumb, containers should not contain anything that is not mandatory for running the application).</em></p><h4>Step 1: Pre-requisites setup</h4><p>We’ll start from the <a href="https://hub.docker.com/_/debian">Debian </a>base image, which is a very clean and widely used linux distribution, so the file will start taking shape, with the first line being:</p><pre>FROM debian:latest as build-app-stage</pre><p>We have also set an <strong>alias</strong> for this stage <em>(build-app-stage)</em>, as we’ll see we need it towards the end.</p><p>Next we’ll add up some useful commands that make our life easier in preparation for the next instructions — make the container use bash when running commands <em>(instead of the standard shell)</em>, and install a package that we are going to use to download stuff from the Internet: curl<em>.</em></p><p>To execute commands when building the image, we use the RUN keyword which basically tells docker that “hey, this command needs to run inside the vm” — in our case, inside the Debian-running vm, so all of them will be Linux/Debian commands.</p><pre># replace shell with bash so we can source files<br>RUN rm /bin/sh &amp;&amp; ln -s /bin/bash /bin/sh<br><br># update the repository sources list and install dependencies<br>RUN apt-get update &amp;&amp; \<br>    apt-get install -y curl &amp;&amp; \<br>    apt-get -y autoclean</pre><p>As said in the <em>theoretical solution</em> section, we need to actually install Node.js <em>(because building the application requires having Node.js)</em>. And we need to have an automated way to do this. And for that, <a href="https://github.com/nvm-sh/nvm"><strong>nvm </strong></a>exists. So, first, we need to install <em>nvm</em>.</p><p>And in order to have access to <em>nvm (don’t you love jumping from one to another?)</em>, which is a tool, we need to download NVM using curl <em>(installed previously)</em> from their release directory on GitHub <em>(the version used in this tutorial is v0.39.7, you can check their </em><a href="https://github.com/nvm-sh/nvm"><em>GitHub page</em></a><em> for latest version)</em>.</p><p><strong><em>Note</em></strong><em>: Internet access required at this step by the environment running the image build, so careful where the building of this file happens, e.g. if you run the docker build on a Jenkins or similar infrastructure, its access to the Internet should not be limited.</em></p><pre>#install nvm<br>ENV NVM_DIR /usr/local/nvm<br>RUN mkdir /usr/local/nvm<br>RUN curl --silent -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash</pre><p>Then, we get to actually install <strong>Node.js</strong>, through nvm.</p><p><strong><em>Note:</em></strong><em> the Node version defined — I used the latest available LTS at the moment of writing this article (20.11.0). You should use the version compatible with your application</em></p><pre># install node and npm<br>ENV NODE_VERSION 20.11.0<br>RUN source $NVM_DIR/nvm.sh \<br>    &amp;&amp; nvm install $NODE_VERSION \<br>    &amp;&amp; nvm alias default $NODE_VERSION \<br>    &amp;&amp; nvm use default<br><br># add node and npm to path so the commands are available<br>ENV NODE_PATH $NVM_DIR/v$NODE_VERSION/lib/node_modules<br>ENV PATH $NVM_DIR/versions/node/v$NODE_VERSION/bin:$PATH<br><br># confirm installation<br>RUN node -v<br>RUN npm -v</pre><p>As you can see, there are also some extra steps here — making sure to add <em>Node </em>and <em>npm</em> to path, so they are available to be executed as commands, and just running each of them with the -v parameter (that shows the version) to confirm that everything is OK <em>(this last part can be easily removed).</em></p><h4>Step 2: Building the application</h4><p>And finally, <strong>we arrive at your application</strong>. Now we need to copy over the application files inside the container, in order to install the node modules, and then build the application.</p><p>This part is split into two parts:</p><ol><li>defining a working directory — we create a directory called src/app in the usr root directory of the container <em>(remember, this is Linux!)</em>. In this directory we will build the application, it will be similar to your local working environment where you cloned the code repository</li><li>copying over into this folder your project-specific files. This is the most important part, as it copies over your actual application files <em>(including the </em><em>package.json file, configuration files, basically everything you have in the directory where your </em><em>Dockerfile is)</em>.</li></ol><pre># Create a work directory<br>RUN mkdir /usr/src/app<br>WORKDIR /usr/src/app<br>ENV PATH /usr/src/app/node_modules/.bin:$PATH<br><br># copy over project-specific files<br>COPY . /usr/src/app</pre><p>Then, we add the command to install the Node Modules themselves. We will use <strong>npm ci </strong>and not <strong>npm i</strong>, because npm ican install different package versions or update packages, when the version of the package is not fixed, whereas nmp ci always installs the exact same version of a package, as it is locked in the package-lock.json file — read more about it on the <a href="https://docs.npmjs.com/cli/v10/commands/npm-ci">npm site</a>.</p><p>Obviously, this step also requires Internet access. With this command, the packages will be searched and installed automatically from <a href="https://www.npmjs.com/">npm’s official package repository</a>. If you use custom, company owned repositories, make sure your project is properly set-up for that — that usually involves defining the sources in a .npmrc file.</p><pre># install all modules<br>RUN npm ci</pre><p>Now, the most natural precursor of the package installation is the actual building of the application. Make sure that your build command <em>(npm)</em> is properly setup in the package.json file and that it statically outputs your application <em>(by default it should be, in most setups, since you’re already running it locally)</em>.</p><pre># build the application<br>RUN npm run build</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/267/1*Tvea3p1tdoSofFPbASq9Qw.png" /><figcaption>now we have a brand new output directory, inside the container</figcaption></figure><p>The output folder might be different based on what tooling you use. Remember that inside the docker container you’re automating the steps that you’d do locally as well, so inside the usr/src/app directory you’ll have the application generate the output files in the same way <em>(and in the same directory) </em>as it would do on local. Mine is configure to output everything in the dist directory, so that’s what I’ll use in the following steps. So make sure to know your output directory name.</p><h4>Step 3: Adding the server component</h4><p>The final step is to integrate <strong>nginx</strong> with all of this and start the server.</p><p>But, before that, we actually need to first create a React-specific <strong>configuration file for nginx</strong> <em>(note that this could need to be updated based on your needs, and you might not need it if your routing and rendering happens server-side)</em>. Why we need this configuration? Well, React handles its own <strong>routing</strong>, so we need to tell the server that instead of trying to handle the routing by itself, as it would normally do, it needs to forward all the paths to the UI, which does its own thing.</p><p>You will need to create a file called nginx.conf in your application directory, alongside the Dockerfile and add this content inside:</p><pre>server {<br>  listen 80;<br>  location / {<br>    root   /usr/share/nginx/html;<br>    index  index.html index.htm;<br>    try_files $uri $uri/ /$uri/ /$uri /index.html;<br>  }<br>  error_page   500 502 503 504  /50x.html;<br>  location = /50x.html {<br>    root   /usr/share/nginx/html;<br>  }<br>}</pre><p>Then, we get to actually setup nginx. For this, we’ll:</p><ol><li>source out the<a href="https://hub.docker.com/_/nginx"> nginx image</a> from Docker Hub inside our <em>Dockerfile</em>, to be used in the final context of the image, which will be the context that actually runs at the end in the container</li><li>feed <em>nginx </em>the <em>configuration file</em> we previously defined</li><li>use the files generated from build stage <em>(which we gave the alias build-app-stage)</em> and put them in the <em>html </em>folder of <em>nginx (this is the folder that the server actually serves). </em>Remember that here, instead of dist you need to use whatever output directory your setup creates.</li><li>start the server</li></ol><pre># change the base image to nginx<br>FROM nginx:1.25.3-alpine<br><br># copy over the configuration file<br>COPY nginx.conf /etc/nginx/conf.d/default.conf<br><br># copy the build directory<br>COPY --from=build-app-stage /usr/src/app/dist /usr/share/nginx/html<br><br># expose the port to the outside world of the container<br>EXPOSE 80<br><br># start the server by running the nginx command<br>CMD [&quot;nginx&quot;, &quot;-g&quot;, &quot;daemon off;&quot;]</pre><h3>Final words</h3><p>You should also add a .dockerignore file to your project — this would prevent the COPY command to copy over unwanted files. For starters, we don’t want the node_modules <em>(your build will be really slow if you copy them)</em> to be copied and neither the dist <em>(your output directory),</em> so the file will simply look like this:</p><pre>node_modules<br>dist</pre><p>Now you can build your image by running docker build . &lt;your-image-name&gt;inside the same directory where you put the Dockerfile. The name given to the image should be something meaningful related to the application name, and following your corporation’s / your standards. Giving a name to the image helps you <a href="https://docs.docker.com/engine/reference/commandline/image_push/">publish </a>it to a registry or <a href="https://docs.docker.com/engine/reference/commandline/container_run/">run </a>it afterwards as a container. If you want to test-run it locally, you can use:</p><pre>docker run - name &lt;your-container-name&gt; -p 6969:80 &lt;your-image-name&gt;</pre><p>(exposing the port 80 - exposed with the <em>EXPOSE </em>command from the <em>Dockerfile — </em>to the <a href="https://www.metricfire.com/blog/what-is-docker-network-host/#:~:text=about%20port%20conflicts.-,What%20is%20a%20Docker%20Network%20Host%3F,namespace%20with%20the%20host%20machine.">host</a> port <em>6969</em>, you can change <em>6969 </em>with anything else).</p><p>You can file the full files from this article in the following gist:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/20fcfe9e21566668753b10a7cb1570e3/href">https://medium.com/media/20fcfe9e21566668753b10a7cb1570e3/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23ec186f0fdb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why your Plex isn’t using Direct Play // Transcoding movies instead]]></title>
            <link>https://medium.com/@foxietamine/why-your-plex-isnt-using-direct-play-transcoding-movies-instead-52afe680a79e?source=rss-115c11394ba2------2</link>
            <guid isPermaLink="false">https://medium.com/p/52afe680a79e</guid>
            <category><![CDATA[plex]]></category>
            <category><![CDATA[movies]]></category>
            <category><![CDATA[subtitles]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[plex-media-server]]></category>
            <dc:creator><![CDATA[thefoxdiaries]]></dc:creator>
            <pubDate>Sun, 07 May 2023 08:47:40 GMT</pubDate>
            <atom:updated>2023-05-07T08:47:40.741Z</atom:updated>
            <content:encoded><![CDATA[<p>If you ever wondered why your Plex Server is always <strong>transcoding</strong>, therefore <strong>stuttering </strong>a lot, your precious movies instead of using <strong>Direct Play</strong>, even if you already tried all the standard solutions online <em>(the formats are OK, every setting is at the right place)</em>, then this story might be for you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Me6YZW0cnscTRHSj" /><figcaption>Photo by <a href="https://unsplash.com/es/@pixelshiftarr?utm_source=medium&amp;utm_medium=referral">Elisabeth Pieringer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I recently found myself in quite a peculiar situation. After I obtained *from totally legal sources* the latest and greatest 4K HDR remasters of the Lord of the Rings Trilogy, I fed them to my Plex Server, and found them totally unplayable. I didn’t want to accept the situation, having such quality material at hand, so I started investigating.</p><p>First I searched for answers online. Settings in the Plex Server were OK. The TV theoretically supports HEVC Main 10 HDR format and TrueHD 7.1 or AAC 5.1 audio, so that could not be the problem either. My server is setup on a PC with a Ryzen 7 processor (AMD card, not NVidia), so it was kindof stuttering a lot when trying to transcode the 4K files with 7.1 audio and subtitles, such as it was unplayable. If I switched the audio to AAC 5.1 it was performing better, but still transcoding! I needed Direct Play for that smooth quality.</p><p>So I started digging into the files. I had some similar movies, which were Direct Playing and not transcoding at all. See below a comparison from Plex Dashboard between The Fellowship (transcoding) and Shutter Island (direct play):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/1*f9M89qgwsekPUMWdkrOMZQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*rcfSzI2yYqr5FmWJBu7Thw.png" /></figure><p>So the difference was either something (again) unsupported in the audio codec, something about the subtitles or something entirely different in the whole file format.</p><p>When using Media Info to scramble with the contents of the file, I couldn’t notice anything huge as in differences or weirdness. But I did spot, after a while at staring at them, that PGS stands for <em>Picture based subtitle format</em>.</p><pre>Text #1<br>ID                                       : 4<br>Format                                   : PGS<br>Muxing mode                              : zlib<br>Codec ID                                 : S_HDMV/PGS<br>Codec ID/Info                            : Picture based subtitle format used on BDs/HD-DVDs</pre><p>I did not have much experience with this subtitle format before (mostly encountered SRT and VobSub), so I googled a little, ended up on <a href="https://forums.plex.tv/t/why-does-plex-transcode-internal-subtitles-pgs-can-i-prevent-it/309545">this thread</a>. As it seems, the PGS support is mixed, and due to how this format works <em>(mostly it being a picture)</em>, it needs to be burned into the main picture for display, unless the player / TV supports it natively.</p><p>So <strong>the solution</strong> is quite simple: if you have PGS subtitles, find a different subtitle format (SRT / VOBSUB) and use it. It totally works, I’m writing this after enjoying a nice 3 hours and 48 minutes of total epicness (and smooth Direct Play!).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52afe680a79e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to migrate from Docker Desktop to Rancher Desktop — the complete guide]]></title>
            <link>https://medium.com/@foxietamine/how-to-migrate-from-docker-desktop-to-rancher-desktop-832253cd55c5?source=rss-115c11394ba2------2</link>
            <guid isPermaLink="false">https://medium.com/p/832253cd55c5</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[rancher-desktop]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[docker-desktop]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[thefoxdiaries]]></dc:creator>
            <pubDate>Sat, 03 Dec 2022 13:03:23 GMT</pubDate>
            <atom:updated>2022-12-03T13:07:46.929Z</atom:updated>
            <content:encoded><![CDATA[<p>with troubleshooting</p><p>You might find yourself and your environment (for development) depending on Docker Desktop, which used to be a nice free tool, but now (rightfully) charges money through a subscription for enterprises (and more recently also increased their prices). So if you want to keep every workflow you’re already doing/using intact but get rid of Docker Desktop at the same time, follow this guide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Bfc9ENyvIUwsYXDn" /><figcaption>Photo by <a href="https://unsplash.com/@rubaitulazad?utm_source=medium&amp;utm_medium=referral">Rubaitul Azad</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><ol><li>Uninstall Docker Desktop (<strong>requires Admin</strong>)</li><li>Open PowerShell, run wsl (or wsl -d docker-desktop) and navigate to /var/lib and if there is still a docker folder there, delete it (rm -rf docker) otherwise there will be errors</li><li>Download and install (<strong>requires Admin</strong>): <a href="https://rancherdesktop.io/">Rancher Desktop</a>. It installs in the %APPDATA%, so make sure to install it in the current’s user folder, not in the Administrator one.</li><li>At first run, you’ll get a pop-up to select the configuration to use. Enable <strong>kubernetes</strong> (latest stable) only if you use kube, and select <strong>dockerd</strong> (not containerd) as engine</li><li>Enable container-host communication by allowing traffic by <a href="https://docs.rancherdesktop.io/faq/#q-can-containers-reach-back-to-host-services-via-hostdockerinternal">running this command</a> in PowerShell (<strong>requires Admin).</strong> From this step forward, no further admin rights are required.</li><li>Go to settings → WSL → and enable your already installed WSL2 distribution (should be Ubuntu) integration</li><li>At this step, you theoretically have access to all the docker and kubectl commands</li><li>The docker desktop wsl volume data might not be deleted after the uninstall and it usually uses a lot of space. You must delete it by running wsl --list -v (and here you will see docker-desktop-data and docker-desktop), and then run wsl --unregister docker-desktop-data and wsl --unregister docker-desktop</li><li>Now start Rancher Desktop, run your scripts (that depend on thedockercommand), build/start your containers etc. Everything should run smoothly. You must build everything again since containers are not cross-engine (if you had mounted data through bound volumes for specific containers, you’ll still have it)</li></ol><h3>Troubleshooting</h3><h4>Startup errors</h4><p>If you get an error at first startup or don’t see a window that prompts you to select the engine OR the version displayed is not 1.6.1+ (or latest displayed on the website), then you have to manually replace the rancher desktop files (no need for admin):</p><ol><li>Go to %AppData$\Local\Programs\Rancher Desktop</li><li>Extract and replace here all the contents of the app. The contents of the app can be found by opening the Setup file with 7zip, and navigating to $PLUGINSDIR → app-64.7z.</li><li>If you ever want to update the application, it will not work from inside the application. But if you follow these manual steps, you’ll have a new version.</li></ol><h4>Kubernetes port conectivity errors</h4><p>If you get a Kubernetes error on port connectivity, go to settings and change the port to something else (and restart)</p><h4>Disk space problems</h4><p>If you had problems with space on C (where wsl defaults its data), follow these next steps to move your data container to another partition:</p><ol><li>Open powershell.</li><li>Close Rancher Desktop. Make sure everything is shut down by running (powershell) wsl --shutdown</li><li>Open powershell and type wsl --list -v. You should see rancher-desktop-data (similar to docker-desktop-data)</li><li>Export the data file to the other partition by running this command (and replacing the path with yours): wsl --export rancher-desktop-data D:\\volumes\\rancher-desktop-data.tar.</li><li>Unregister the existing data file by running esl --unregister rancher-desktop-data.</li><li>Import the new location for the data by running (and replacing the path with yours): wsl --import rancher-desktop-data D:\\volumes\\ D:\\volumes\\rancher-desktop-data.tar --version 2. Wait a while. Then test with wsl --list -v to see the data appears.</li><li>Start back Rancher Desktop. You should have all your containers in place but using the new location.</li></ol><h3>Possible downsides and things to consider</h3><ol><li>Rancher Desktop has built-in commands and container management UI when upping them with docker-compose. On plain containers, it doesn’t have any management UI working (so hard to re-start, stop etc.). But tools like the VSCode <a href="https://code.visualstudio.com/docs/containers/overview">Docker Extension</a> — which is fast — , <a href="https://dockstation.io/">DockerStation</a> — which offers a nice UI but is a bit slow — or <a href="https://github.com/jesseduffield/lazydocker">Lazy Docker</a> — a console-like UI — can do the task.</li><li>Any applications that were dependent on Docker Desktop specifics (e.g. using the exposed TCP daemon or specific non-standard commands) will stop working and will need workarounds (like creating new containers to expose the port)</li><li>For logs, either use docker logs -f &lt;container-name&gt;, the UI tool from point (a) or install ELK in your system and see all the logs in Kibana (kibana should be the preferred option)</li><li>host.docker.internal, if you’re using it, might still work. But if it doesn’t (especially on Windows), you will need alternatives. For example, if running an nginx server to bind together one app running locally and one running as a container (e.g. to debug a web application in VSCode), you will need to download nginx into a folder from <a href="http://nginx.org/en/download.html">here</a> (make sure to download the same version you’re using containerized) and update your nginx.conf file to do all the proxying to [localhost](&lt;http://localhost&gt;) (since it’s running on localhost)</li><li>To restart all containers either use the UI tool from point (1) or from powershell/bash: docker restart $(docker ps -a -q)</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=832253cd55c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UI Tests for React using JEST — most common testing patterns (part 4)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@foxietamine/ui-tests-for-react-using-jest-most-common-testing-patterns-part-4-54aa32724364?source=rss-115c11394ba2------2"><img src="https://cdn-images-1.medium.com/max/2600/0*E70QuFDERtSiNgMA" width="4515"></a></p><p class="medium-feed-snippet">This chapter in the React/Jest saga provides an extensive list of examples of various types of tests and common usages of the testing&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@foxietamine/ui-tests-for-react-using-jest-most-common-testing-patterns-part-4-54aa32724364?source=rss-115c11394ba2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@foxietamine/ui-tests-for-react-using-jest-most-common-testing-patterns-part-4-54aa32724364?source=rss-115c11394ba2------2</link>
            <guid isPermaLink="false">https://medium.com/p/54aa32724364</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[jest]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[thefoxdiaries]]></dc:creator>
            <pubDate>Sat, 10 Sep 2022 13:39:05 GMT</pubDate>
            <atom:updated>2022-09-10T13:39:05.137Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[UI Tests for React using JEST — the secret to making your components’ testing easier (part 3)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@foxietamine/ui-tests-for-react-using-jest-the-secret-to-making-your-components-testing-easier-part-3-3390e3b8aa14?source=rss-115c11394ba2------2"><img src="https://cdn-images-1.medium.com/max/2600/0*qn8Bv6f8ak2qdxKj" width="5042"></a></p><p class="medium-feed-snippet">This chapter in the React/Jest saga provides you with a baseline on how to add some helpers to your project that can make your testing&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@foxietamine/ui-tests-for-react-using-jest-the-secret-to-making-your-components-testing-easier-part-3-3390e3b8aa14?source=rss-115c11394ba2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@foxietamine/ui-tests-for-react-using-jest-the-secret-to-making-your-components-testing-easier-part-3-3390e3b8aa14?source=rss-115c11394ba2------2</link>
            <guid isPermaLink="false">https://medium.com/p/3390e3b8aa14</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[jest]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[thefoxdiaries]]></dc:creator>
            <pubDate>Sat, 30 Jul 2022 09:45:02 GMT</pubDate>
            <atom:updated>2022-09-10T13:39:55.477Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[UI Tests for React using JEST — Project Configuration, explained (part 2)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@foxietamine/ui-tests-for-react-using-jest-project-configuration-explained-part-2-7955d0fc43fe?source=rss-115c11394ba2------2"><img src="https://cdn-images-1.medium.com/max/2600/0*ySV6PLyWlkHPK00O" width="5184"></a></p><p class="medium-feed-link"><a href="https://medium.com/@foxietamine/ui-tests-for-react-using-jest-project-configuration-explained-part-2-7955d0fc43fe?source=rss-115c11394ba2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@foxietamine/ui-tests-for-react-using-jest-project-configuration-explained-part-2-7955d0fc43fe?source=rss-115c11394ba2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7955d0fc43fe</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[jest]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[thefoxdiaries]]></dc:creator>
            <pubDate>Sat, 01 May 2021 14:30:55 GMT</pubDate>
            <atom:updated>2022-09-10T13:40:35.428Z</atom:updated>
        </item>
    </channel>
</rss>