From f4efe4a463f87bc0c1fb3b19f87363731e8601ca Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?batuhan=20i=C3=A7=C3=B6z?= Date: Sun, 15 Nov 2026 18:34:10 +0100 Subject: [PATCH 1/2] Say that each version stores spacefast.config.ts and who can read it --- content/(reference)/config-file.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/(reference)/config-file.mdx b/content/(reference)/config-file.mdx index 5ee467e..9e5140c 100644 --- a/content/(reference)/config-file.mdx +++ b/content/(reference)/config-file.mdx @@ -222,6 +222,8 @@ Two command groups take an explicit path. The server does not run TypeScript. When `sf publish` or `sf build` packs a version, the CLI evaluates `spacefast.config.ts`. It writes the result into the version as `sf.jsonc`, in place of any `sf.jsonc` on disk. Your source files do not change. +The CLI also stores your `spacefast.config.ts` in the version, as `.spacefast/config-source.ts`, so each version shows which config produced it. It is never served. Your team can read it with the version's files. If you make the Space's source available, anyone can read it in the public source. Keep tokens and internal URLs out of the file and read them from Space variables. The first time you publish with the source available, `sf publish` warns you once. + Files that the config imports are ordinary files. If they are in the published directory, they are published and served. Hosted Git builds run the same CLI build, so they evaluate a committed `spacefast.config.ts` too. From d9acf388c0ddf014abc1ab4e210bb49bcfcbdba8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?batuhan=20i=C3=A7=C3=B6z?= Date: Sun, 15 Nov 2026 20:46:30 +0100 Subject: [PATCH 2/2] Say the config is public through the source's main branch --- content/(reference)/config-file.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/(reference)/config-file.mdx b/content/(reference)/config-file.mdx index 9e5140c..2916f2f 100644 --- a/content/(reference)/config-file.mdx +++ b/content/(reference)/config-file.mdx @@ -222,7 +222,7 @@ Two command groups take an explicit path. The server does not run TypeScript. When `sf publish` or `sf build` packs a version, the CLI evaluates `spacefast.config.ts`. It writes the result into the version as `sf.jsonc`, in place of any `sf.jsonc` on disk. Your source files do not change. -The CLI also stores your `spacefast.config.ts` in the version, as `.spacefast/config-source.ts`, so each version shows which config produced it. It is never served. Your team can read it with the version's files. If you make the Space's source available, anyone can read it in the public source. Keep tokens and internal URLs out of the file and read them from Space variables. The first time you publish with the source available, `sf publish` warns you once. +The CLI also stores your `spacefast.config.ts` in the version, as `.spacefast/config-source.ts`, so each version shows which config produced it. It is never served. Your team can read it with the version's files. `spacefast.config.ts` is also part of your source, so if you make the Space's source available, anyone can read it on the source's main branch. Keep tokens and internal URLs out of the file and read them from Space variables. The first time you publish to a Space whose source is available, `sf publish` warns you once. Files that the config imports are ordinary files. If they are in the published directory, they are published and served.