<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Guides on</title><link>https://deploy-preview-3620--amazing-golick-2d0138.netlify.app/docs/guides/</link><description>Recent content in Guides on</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 02 Aug 2026 14:52:50 +0200</lastBuildDate><atom:link href="https://deploy-preview-3620--amazing-golick-2d0138.netlify.app/docs/guides/index.xml" rel="self" type="application/rss+xml"/><item><title>Guide: docker compose</title><link>https://deploy-preview-3620--amazing-golick-2d0138.netlify.app/docs/guides/docker-compose/</link><pubDate>Sun, 01 Aug 2021 22:10:01 +0200</pubDate><guid>https://deploy-preview-3620--amazing-golick-2d0138.netlify.app/docs/guides/docker-compose/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_docker_compose"&gt;Docker Compose&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;In this scenario, we have to maintain a docker-compose file and we want to be sure that we always use the latest available docker.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Guide: Npm</title><link>https://deploy-preview-3620--amazing-golick-2d0138.netlify.app/docs/guides/npm/</link><pubDate>Tue, 07 Feb 2023 22:10:01 +0200</pubDate><guid>https://deploy-preview-3620--amazing-golick-2d0138.netlify.app/docs/guides/npm/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_npm"&gt;npm&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="sect2"&gt;
&lt;h3 id="_goal"&gt;Goal&lt;/h3&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;The purpose of this pipeline is to track one npm dependency update, and then update both the package.json and package-lock.json in case of a version change.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Guide: helm chart</title><link>https://deploy-preview-3620--amazing-golick-2d0138.netlify.app/docs/guides/helm-chart/</link><pubDate>Sun, 27 Feb 2022 22:10:01 +0200</pubDate><guid>https://deploy-preview-3620--amazing-golick-2d0138.netlify.app/docs/guides/helm-chart/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_helm_chart"&gt;Helm Chart&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Helm is a popular package manager for deploying applications on Kubernetes.
But, those packages can be outdated quickly.
In this guide we explore how we can automatically update Helm charts based on third-party dependencies.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Guide: dockerfile</title><link>https://deploy-preview-3620--amazing-golick-2d0138.netlify.app/docs/guides/dockerfile/</link><pubDate>Fri, 20 Sep 2024 22:10:01 +0200</pubDate><guid>https://deploy-preview-3620--amazing-golick-2d0138.netlify.app/docs/guides/dockerfile/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_dockerfile"&gt;Dockerfile&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="sect2"&gt;
&lt;h3 id="_goal"&gt;Goal&lt;/h3&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;This guide analyzes how the Jenkins project automates its Dockerfile file updates.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;It’s one thing to publish a Docker image, but it’s another one to maintain it over time.&lt;/p&gt;
&lt;/div&gt;</description></item></channel></rss>