How Multi-Stage Builds and Slim Base Images Slash Docker Image Size

·1 views

Oversized Docker images slow down deployments, waste storage, and expand the attack surface for security threats. Developers can significantly reduce image size by choosing minimal base images such as Alpine or python-slim instead of full OS images. Multi-stage builds allow build tools and dependencies to be used during compilation without being included in the final image, keeping only the necessary binaries or artifacts. Combining cleanup commands within a single RUN instruction prevents deleted files from persisting in intermediate layers. Additional techniques like using a .dockerignore file and adopting distroless runtime images further trim size and improve security posture.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How a naive regex silently logged plugin versions as WordPress core versions

A developer discovered that scraping WordPress core version numbers from the update-core.php admin page could silently return wrong values, because the page also displays version numbers for pending plugin updates. A simple regex matching the first version-shaped number on the page picked up a plugin's version string, such as 1.7.11, instead of the actual WordPress core version. The bug produced no errors, making it hard to detect until someone noticed the reported version had never existed in WordPress core's release history. The recommended fix involves a three-layer approach: prioritising specific DOM selectors, falling back to keyword-anchored regex, and validating that the extracted major version number falls within the known WordPress core range of 4 to 9. The case highlights a broader principle that a successful regex match does not guarantee the matched value is semantically correct.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Recreates Mother's Telugu Sunday Meal as Accessible CSS-Only Landing Page

A developer built a CSS-only interactive landing page inspired by their mother's traditional Telugu Sunday meal served on a banana leaf. The page features sixteen dishes arranged in authentic serving order, allowing users to tap any dish to navigate directly to that course or scroll through the meal sequentially. Every visual element on the page is rendered purely in CSS, with no images, SVG, or canvas used. Accessibility was prioritised from the outset, with heading order, tab order, and reading order all mirroring the traditional eating sequence, and Telugu dish names tagged with the correct language attribute for accurate screen-reader pronunciation. The project was submitted to the Frontend Challenge Comfort Food Edition, with the developer noting that the meal's thirty-year-old structure provided a ready-made information architecture that simply needed to be preserved.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Details 10 Lessons From Migrating WordPress Sites to Cloudflare Pages

A developer recently migrated ten WordPress sites from a shared LAMP host to Cloudflare Pages as static exports, citing benefits like free hosting, no server maintenance, and built-in CDN coverage. The process involved crawling each live site with wget and a custom tool, then deploying the static file output via Wrangler — no build framework required. However, several issues emerged post-migration, including broken canonical tags where relative URLs collapsed to the site root, causing Google Search Console to flag most inner pages as duplicates. A scripted fix was needed to rewrite all canonical hrefs to fully qualified absolute URLs across the exported HTML files, a bug found on three of the ten sites. Additionally, dynamically generated XML sitemaps from WordPress SEO plugins were absent from the static export, requiring sitemaps to be rebuilt by walking the file tree and resubmitted manually to Google Search Console.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Tutorial: Build a Personal Health RAG System Using Apple HealthKit and Pinecone

A new developer tutorial published on DEV Community walks through building a Retrieval-Augmented Generation (RAG) pipeline for personal health data. The guide uses Apple HealthKit and Google Health Connect exports as source data, processing them with DuckDB to downsample high-frequency metrics like heart rate before vectorization. LangChain and OpenAI Embeddings are then used to convert structured health summaries into searchable vector documents stored in Pinecone. The end result is a system that allows users to query their own biometric history using natural language questions. The tutorial targets Python 3.10+ developers and requires API access to Pinecone and OpenAI.

0 comments Read more at DEV Community