From 87ffbfea6b7421ea751d6d185add0c598a01aedf Mon Sep 17 00:00:00 2001 From: krls2020 Date: Thu, 11 Jun 2026 10:48:32 +0200 Subject: [PATCH 1/2] docs: fix --deploy-git-folder description + document buildFromGit constraints and startWithoutCode - pipeline.mdx: the --deploy-git-folder flag description was a copy of --zerops-yaml-path's text. Corrected to what the flag does per 'zcli service deploy --help': uploads the .git folder with the deploy (ignored by default). - import.mdx buildFromGit: document two constraints verified against the live platform: the repository must be publicly accessible (a private repo fails at clone time with a FAILED build and no build log), and the URL must not carry a trailing .git suffix (fails the same way). - import.mdx: add the startWithoutCode service key (present in the live import JSON schema, previously undocumented): starts a runtime service's containers without waiting for a first deploy. --- apps/docs/content/features/pipeline.mdx | 4 ++-- apps/docs/content/references/import.mdx | 13 +++++++++++++ 2 files changed, 15 insertions(+), 2 deletions(-) diff --git a/apps/docs/content/features/pipeline.mdx b/apps/docs/content/features/pipeline.mdx index dac08a59..6c86f18b 100644 --- a/apps/docs/content/features/pipeline.mdx +++ b/apps/docs/content/features/pipeline.mdx @@ -405,8 +405,8 @@ Usage: Flags: --archive-file-path string If set, zCLI creates a tar.gz archive with the application code in the required path relative to the working directory. By default, no archive is created. - --deploy-git-folder Sets a custom path to the zerops.yaml file relative to the working directory. By default zCLI - looks for zerops.yaml in the working directory. + --deploy-git-folder If set, the .git folder is also uploaded with the deploy. By default, the .git folder + is ignored. -h, --help the service deploy command. --project-id string If you have access to more than one project, you must specify the project ID for which the command is to be executed. diff --git a/apps/docs/content/references/import.mdx b/apps/docs/content/references/import.mdx index cea9050d..f8558d8f 100644 --- a/apps/docs/content/references/import.mdx +++ b/apps/docs/content/references/import.mdx @@ -401,6 +401,19 @@ This example includes all possible configuration options for Zerops services. No string (URL) A URL of a Github or Gitlab repository used for a one-time build of your service. + The repository must be publicly accessible — a private repository fails at clone + time (the build ends FAILED with no build log). Use the plain repository URL + without a trailing `.git` suffix, which fails the same way. + + + + startWithoutCode + boolean + + Default: `false`
+ Set `true` to start a runtime service's containers without waiting for a first + deploy. Useful for provisioning a service whose code arrives later (e.g. via + SSH or a later pipeline run). From 4ed7046aa3c72c751fe88122a197d64c4e03fbfa Mon Sep 17 00:00:00 2001 From: krls2020 Date: Thu, 18 Jun 2026 17:05:12 +0200 Subject: [PATCH 2/2] =?UTF-8?q?docs(import):=20expand=20startWithoutCode?= =?UTF-8?q?=20use=20case=20to=20the=20SSH-experiment=20=E2=86=92=20run.pre?= =?UTF-8?q?pareCommands=20workflow?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per review on PR #350: startWithoutCode is also the on-ramp for getting a bare runtime container to SSH into and experiment in, then versioning the setup steps into run.prepareCommands so they persist across container replacements (SSH changes alone are non-persistent). Cross-links the SSH reference and the zerops.yaml run.prepareCommands spec anchor. --- apps/docs/content/references/import.mdx | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/apps/docs/content/references/import.mdx b/apps/docs/content/references/import.mdx index f8558d8f..84c9e721 100644 --- a/apps/docs/content/references/import.mdx +++ b/apps/docs/content/references/import.mdx @@ -412,8 +412,11 @@ This example includes all possible configuration options for Zerops services. No Default: `false`
Set `true` to start a runtime service's containers without waiting for a first - deploy. Useful for provisioning a service whose code arrives later (e.g. via - SSH or a later pipeline run). + deploy. Useful when the code arrives later (a subsequent pipeline run), or when + you want a live container to [SSH](/references/networking/ssh) into and play + around in — once your setup steps work, version them into + [`run.prepareCommands`](/zerops-yaml/specification#preparecommands--1) so they + persist across container replacements.