<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Devops on Kaisekukun</title><link>https://netguide.jp/en/tags/devops/</link><description>Recent content in Devops on Kaisekukun</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Kaisekukun</copyright><lastBuildDate>Wed, 15 Apr 2026 12:00:00 +0900</lastBuildDate><atom:link href="https://netguide.jp/en/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Accelerating GitHub Actions CI/CD workflows using Caching</title><link>https://netguide.jp/en/software/github-actions-cicd-caching/</link><pubDate>Wed, 15 Apr 2026 12:00:00 +0900</pubDate><guid>https://netguide.jp/en/software/github-actions-cicd-caching/</guid><description>&lt;img src="https://netguide.jp/img/thumbnail/github-actions-cicd-caching-en.png" alt="Featured image of post Accelerating GitHub Actions CI/CD workflows using Caching" /&gt;&lt;p&gt;Optimizing CI/CD workflow times directly impacts developer productivity and reduces computing expenses. This article shows you how to integrate dependency caching in GitHub Actions, helping you slash compilation and package setup times.&lt;/p&gt;
&lt;p&gt;We provide YAML workflow templates for Node.js, Python, and Rust, alongside best practices to ensure optimal cache hits.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="1-why-cache-dependencies-in-cicd"&gt;1. Why Cache Dependencies in CI/CD?
&lt;/h2&gt;&lt;p&gt;When a CI agent starts without caching, it spins up a clean container and fetches every dependency from package registries. This introduces several drawbacks:&lt;/p&gt;</description></item><item><title>Docker Container Image Security Best Practices</title><link>https://netguide.jp/en/software/docker-container-security/</link><pubDate>Tue, 10 Mar 2026 12:00:00 +0900</pubDate><guid>https://netguide.jp/en/software/docker-container-security/</guid><description>&lt;img src="https://netguide.jp/img/thumbnail/docker-container-security-en.png" alt="Featured image of post Docker Container Image Security Best Practices" /&gt;&lt;p&gt;In modern cloud-native development, &lt;strong&gt;Docker containers&lt;/strong&gt; are the default standard for deploying web applications.&lt;/p&gt;
&lt;p&gt;However, generic Dockerfiles often yield images containing OS vulnerabilities, unnecessary tooling, or root process privileges. In this guide, we cover the essential best practices to harden your Docker container images for production.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id="1-enforce-multi-stage-builds"&gt;1. Enforce Multi-stage Builds
&lt;/h3&gt;&lt;p&gt;Leaving build tools, compiler caches, or developer dependencies (like npm or git) inside your final runtime image increases the container size and broadens the attack surface.&lt;/p&gt;</description></item></channel></rss>