From d27c953b4b3f1a1cf10eb40ad67ae315e97c6eb1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ale=C5=A1?= Date: Tue, 31 Mar 2026 19:01:15 +0200 Subject: [PATCH] chore(guides): update 1 guides --- apps/docs/content/guides/build-cache.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/apps/docs/content/guides/build-cache.mdx b/apps/docs/content/guides/build-cache.mdx index 1d42f7ef..2c994cb6 100644 --- a/apps/docs/content/guides/build-cache.mdx +++ b/apps/docs/content/guides/build-cache.mdx @@ -3,12 +3,11 @@ title: "Build Cache" description: "Zerops uses a two-layer build cache: base layer (OS + prepareCommands) and build layer (buildCommands output). The `cache:` attribute in zerops.yml controls which files persist between builds. Changing `build.os`, `build.base`, `build.prepareCommands`, or `build.cache` invalidates both layers (cascade)." --- - ## Keywords build cache, cache, invalidation, prepareCommands, buildCommands, base layer, build layer, node_modules, vendor, cache paths, cache true, cache false, build speed, build optimization, two-layer cache, cascade invalidation ## TL;DR -Zerops uses a two-layer build cache: base layer (OS + prepareCommands) and build layer (buildCommands output). The `cache:` attribute in zerops.yml controls which files persist between builds. Changing `build.os`, `build.base`, `build.prepareCommands`, or `build.cache` invalidates both layers (cascade). +Zerops uses a two-layer build cache: base layer (OS + prepareCommands output) and build layer (buildCommands output). The `cache:` attribute in zerops.yml controls which files persist between builds. Changing `build.os`, `build.base`, `build.prepareCommands`, or `build.cache` invalidates both layers (cascade). ---