0 views collected around this technical thread.
The article explains how to build a custom Webpack plugin that uploads compiled static assets to a CDN, rewrites public‑path references to CDN URLs, and employs a hash‑based cache file to skip unchanged files, cutting build time from 40 seconds to 17 seconds in large projects.
The article explains why static assets of a single‑page frontend application disappear after a container restart, analyzes the root cause, and presents a practical solution that stores assets on an external file server or CDN while keeping only index.html inside the container, thereby eliminating 404 errors caused by missing resources.
Since Go 1.16, the //go:embed directive allows developers to embed files, directories, or entire static assets directly into the compiled binary, simplifying deployment; this article explains the directive, its three embedding methods, usage in HTTP servers, unit tests, handling parent directories, and important considerations.
Tencent Video slashed static image bandwidth costs by over 60% using AVIF compression and on‑the‑fly image sampling, which together cut average image size by more than half, reduced memory, latency and decode time, and saved tens of millions of yuan across billions of daily requests.
The article recounts a real‑world CDN failure that broke the passjava.cn site, explains what a CDN is, and details step‑by‑step recovery actions—including downloading assets, using alternative storage, and refreshing a new CDN—to get the site back online.
Static and dynamic resource separation, commonly known as static‑dynamic separation, involves deploying static files (HTML, JavaScript, CSS, images) on a web server like Nginx while forwarding dynamic requests to a backend application server via reverse proxy, thereby improving static asset delivery speed and enabling parallel front‑end and back‑end development.
This guide explains how to install Nginx on Linux, serve a built Angular/React/Vue frontend from the server's static directory, and configure Nginx as a reverse proxy to forward API requests to a backend service, completing the setup with a service restart.
The article explains the concept of static/dynamic separation, compares deployment methods such as Nginx and CDN, discusses domain strategies, outlines its benefits and drawbacks, and presents an architecture suitable for high‑traffic static content delivery.