<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Docker on The Final Artefact</title><link>https://www.thefinalartefact.xyz/tags/docker/</link><description>Recent content in Docker on The Final Artefact</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Thu, 30 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.thefinalartefact.xyz/tags/docker/index.xml" rel="self" type="application/rss+xml"/><item><title>Building Apache Superset Home Setup</title><link>https://www.thefinalartefact.xyz/post/building-apache-superset-home-setup/</link><pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.thefinalartefact.xyz/post/building-apache-superset-home-setup/</guid><description>&lt;p&gt;&lt;a href="https://www.thefinalartefact.xyz/post/building-apache-superset-home-setup/images/apache-superset-chart-editor.png" target="_blank" rel="noopener noreferrer"&gt;
&lt;img alt="Apache Superset chart editor showing a stacked area chart for synthetic transaction data" loading="lazy" src="https://www.thefinalartefact.xyz/post/building-apache-superset-home-setup/images/apache-superset-chart-editor.png"&gt;
&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="background"&gt;Background&lt;/h2&gt;
&lt;p&gt;I was recently asked to help, pro bono, with analysing some life science data. From the outset I expected a steady stream of feedback along the lines of &lt;em&gt;can you show this like that&lt;/em&gt;, and that prospect pulled me back to my early career days working as a researcher and analyst for various outfits. What those years taught me is that the bottleneck is rarely the analysis itself; it is the loop of sharing a result, hearing how someone would prefer to see it, and turning that around quickly. A small, self-service tool that lets people poke at the data themselves removes most of that friction.&lt;/p&gt;</description></item><item><title>One Line Docker Commands</title><link>https://www.thefinalartefact.xyz/post/one-line-docker/</link><pubDate>Wed, 19 Mar 2025 00:00:00 +0000</pubDate><guid>https://www.thefinalartefact.xyz/post/one-line-docker/</guid><description>&lt;p&gt;&lt;a href="https://www.thefinalartefact.xyz/post/one-line-docker/images/ast_docker.png" target="_blank" rel="noopener noreferrer"&gt;
&lt;img alt="Executing Python command across multiple versions" loading="lazy" src="https://www.thefinalartefact.xyz/post/one-line-docker/images/ast_docker.png"&gt;
&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Setting up a robust data science development environment takes time, and it&amp;rsquo;s a process that’s rarely ever finished. If you’re the type who likes to get the most out of your tools, you’ll likely enjoy tweaking, optimising, and layering your workspace with productivity enhancements. That might mean refining your Python setup to easily manage multiple language versions and dependencies, or expanding your text editor with plugins for linting, code suggestions, unit test execution, and CI/CD integration.&lt;/p&gt;</description></item><item><title>Installing Hortonworks Sanbox on Mac with Docker</title><link>https://www.thefinalartefact.xyz/post/installing-hortonworks-sanbox-deployment-hdp-on-docker-mac/</link><pubDate>Sat, 23 Feb 2019 00:00:00 +0000</pubDate><guid>https://www.thefinalartefact.xyz/post/installing-hortonworks-sanbox-deployment-hdp-on-docker-mac/</guid><description>&lt;h2 id="background"&gt;Background&lt;/h2&gt;
&lt;p&gt;The post covers installation of Hortonworks Sandbox (HD) on Mac using Docker. In software development, &lt;em&gt;sandbox&lt;/em&gt; describes a testing environment that can be used to isolate untested code changes from a production code. Hortonworks Sandbox provides such an environment with the Hortonworks Data Platform installed. Hortonworks Data Platform is an open source framework facilitating distributed storage and processing large volumes of data.&lt;/p&gt;
&lt;p&gt;Deploying system for distributed processing &lt;em&gt;within&lt;/em&gt; a single computer may seem like a counter-intuitive idea but it&amp;rsquo;s actually a very common practice. Most frequent use cases involve various learning / professional development activities where one may be interested in learning new technology or simply exploring available interfaces. Other frequent use case pertains to various demos, where there may be a need to demonstrate product capabilities and accessing proper, production environment could be cumbersome.&lt;/p&gt;</description></item></channel></rss>