<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>BigHaus</title><link>https://bighaus.nl/</link><description>Recent content on BigHaus</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 13 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://bighaus.nl/index.xml" rel="self" type="application/rss+xml"/><item><title>From docker-compose to Kubernetes with k3s</title><link>https://bighaus.nl/writing/docker-compose-to-kubernetes-k3s/</link><pubDate>Sat, 13 Jun 2026 00:00:00 +0000</pubDate><guid>https://bighaus.nl/writing/docker-compose-to-kubernetes-k3s/</guid><description>&lt;p&gt;If you can write a &lt;code&gt;docker-compose.yml&lt;/code&gt;, you already understand most of Kubernetes. The concepts translate almost one-to-one — they&amp;rsquo;re just spelled differently. k3s is a lightweight distribution that runs the same Kubernetes you&amp;rsquo;d find in production, without needing a beefy server or a complicated setup. It works great on a laptop and equally well on a small VPS.&lt;/p&gt;
&lt;p&gt;By the end of this article you&amp;rsquo;ll have nginx running with a Deployment, a Service, and an Ingress. Those three resources are the foundation of pretty much every app you&amp;rsquo;ll deploy on Kubernetes.&lt;/p&gt;</description></item><item><title>Kubernetes for the rest of us</title><link>https://bighaus.nl/writing/kubernetes-for-the-rest-of-us/</link><pubDate>Sat, 13 Jun 2026 00:00:00 +0000</pubDate><guid>https://bighaus.nl/writing/kubernetes-for-the-rest-of-us/</guid><description>&lt;p&gt;A practical guide to setting up and running a production-grade Kubernetes cluster — written for developers, not ops teams.&lt;/p&gt;</description></item><item><title>BigHaus</title><link>https://bighaus.nl/work/big-haus/</link><pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate><guid>https://bighaus.nl/work/big-haus/</guid><description>&lt;p&gt;BigHaus is my personal brand for IT work — and the platform behind it is built to match. Rather than delegating to managed hosting, I run a self-hosted K3s cluster in production, giving full ownership and control over the stack and its costs.&lt;/p&gt;
&lt;h4 id="approach"&gt;Approach&lt;/h4&gt;
&lt;p&gt;The goal was a GitOps platform: every service declared in version control, every change applied automatically. Getting K3s, a Dockerized Hugo site, Mailu for mail, Cert-Manager with Let&amp;rsquo;s Encrypt, and ArgoCD to operate as a coherent whole was the core challenge — not any single service, but the discipline of making them all declarative and self-healing. ArgoCD watches the repository and reconciles cluster state on every push, so deployments require no manual intervention.&lt;/p&gt;</description></item><item><title>Duurzame Bouwkeet</title><link>https://bighaus.nl/work/duurzame-bouwkeet/</link><pubDate>Wed, 01 May 2024 00:00:00 +0000</pubDate><guid>https://bighaus.nl/work/duurzame-bouwkeet/</guid><description>&lt;p&gt;Duurzame Bouwkeet builds off-grid and CO₂-neutral construction site offices for major Dutch enterprises. Their clients needed to control climate, lighting, and connected devices from a compact wall-mounted touchscreen — no keyboard, no technical knowledge assumed, running entirely on-device.&lt;/p&gt;
&lt;h4 id="approach"&gt;Approach&lt;/h4&gt;
&lt;p&gt;I was brought in as a freelance developer to build the frontend from scratch. Bundle size mattered here: the app runs directly on the touchscreen hardware, so I chose Svelte for its minimal runtime footprint and gentle learning curve — keeping the app fast on constrained hardware while ensuring any future developer could maintain it without friction. Real-time energy supply data and device state had to update instantly, which made WebSockets the only real option over the Node.js backend. Rather than polling, device changes are triggered via events — immediate feedback in a context where delayed response would feel broken.&lt;/p&gt;</description></item><item><title>Dutch Customs Integration</title><link>https://bighaus.nl/work/dutch-customs-integration/</link><pubDate>Sat, 01 Jun 2019 00:00:00 +0000</pubDate><guid>https://bighaus.nl/work/dutch-customs-integration/</guid><description>&lt;p&gt;Newminds built a customs integration for clients in the Dutch agricultural trade sector — specifically businesses dealing in potatoes and onions, where seasonal export volumes are high and documentation requirements are strict. Before the integration existed, shipping staff manually re-entered data from their ERP into a third-party customs handling platform to generate documents like EUR1 certificates and CVOs. The process was slow, error-prone, and bottlenecked heavily during peak export season.&lt;/p&gt;</description></item><item><title>AGRIO</title><link>https://bighaus.nl/work/agrio/</link><pubDate>Sat, 01 Sep 2018 00:00:00 +0000</pubDate><guid>https://bighaus.nl/work/agrio/</guid><description>&lt;p&gt;AGRIO is a vertical ERP extension built on top of Microsoft Business Central, purpose-built for the agricultural trade sector. The platform automates the full chain from field to factory — sampling, sorting, transport planning, quality control, and production — for traders and trade houses across Europe dealing in field crops like potatoes and onions. I joined the AGRIO team at Newminds in September 2018, working on the product for three years as both a software engineer and product specialist.&lt;/p&gt;</description></item><item><title>About</title><link>https://bighaus.nl/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://bighaus.nl/about/</guid><description>&lt;p&gt;I&amp;rsquo;m Daniël — software engineer behind &lt;strong&gt;BigHaus&lt;/strong&gt;, building the web since 2016.&lt;/p&gt;
&lt;h2 id="stack"&gt;Stack&lt;/h2&gt;
&lt;p&gt;My Day to day is a mix of Vue/Nuxt, TypeScript, Java and Kubernetes. Comfortable across the whole pipeline — from CSS grid quirks to cluster management.&lt;/p&gt;
&lt;h2 id="now"&gt;Now&lt;/h2&gt;
&lt;p&gt;Working as a Software Engineer @&lt;a href="https://www.trimm.nl"&gt;TRIMM&lt;/a&gt; where I get to build awesome websites, apps and tools for a range of clients.&lt;/p&gt;
&lt;h2 id="bighaus"&gt;BigHaus?&lt;/h2&gt;
&lt;p&gt;It&amp;rsquo;s a play on words: &amp;ldquo;Big&amp;rdquo; and &amp;ldquo;Haus&amp;rdquo; (German for &amp;ldquo;house&amp;rdquo;) means essentially a big house. If you translate it in Dutch, you&amp;rsquo;ll get &amp;ldquo;Groot Huis&amp;rdquo;, which is a pun on my name, being Daniël Groothuis.&lt;/p&gt;</description></item></channel></rss>