diff --git a/cloud_docs/concepts/app-publishing.md b/cloud_docs/concepts/app-publishing.md index bcea8323..2b5880b0 100644 --- a/cloud_docs/concepts/app-publishing.md +++ b/cloud_docs/concepts/app-publishing.md @@ -5,7 +5,7 @@ description: Serverpod Cloud builds your Flutter app and uploads it to TestFligh # App publishing -Getting a Flutter app to testers means signing builds, matching store settings, and uploading to TestFlight and Google Play. With app publishing, you run one command: Serverpod Cloud builds your Flutter app for iOS and Android, signs it, and uploads it to the stores you connected in the console. +Getting a Flutter app to testers means signing builds, matching store settings, and uploading to TestFlight and Google Play. With app publishing, you run one command, and Serverpod Cloud builds your Flutter app for iOS and Android, signs it, and uploads it to the stores you connected in the console. You publish from the Cloud CLI. The `app setup` command prepares your Flutter app for the stores, and the `app doctor` command checks your app's setup before you publish and tells you how to fix each problem it finds. @@ -84,7 +84,7 @@ iOS 1 check failed. Fix it before you publish the app. ``` -A check marked `✗` makes the build or the upload fail, so fix it before you publish. A check marked `!` is a warning: the app can be published, but the result may not be what you want. +A check marked `✗` makes the build or the upload fail, so fix it before you publish. A check marked `!` is a warning. The app can be published, but the result may not be what you want. The command finds your Flutter app from `project.app.dir` in `scloud.yaml`, the current directory, or your server's workspace. Pass `--app-dir` to check an app somewhere else, and `--platforms ios` or `--platforms android` to check one platform. diff --git a/cloud_docs/concepts/deployment-hooks.md b/cloud_docs/concepts/deployment-hooks.md index 2dfdb620..a43a7eb3 100644 --- a/cloud_docs/concepts/deployment-hooks.md +++ b/cloud_docs/concepts/deployment-hooks.md @@ -57,7 +57,7 @@ The `pre_deploy` and `post_deploy` hooks fail asymmetrically: - A failing `pre_deploy` script aborts the deploy *before* Cloud receives your code. - A `post_deploy` script runs *after* the upload, before Cloud finishes building and rolling out the new version. If it fails, the `serverpod cloud deploy` command exits with an error, but Cloud keeps deploying. Check the result with `serverpod cloud status deployment show`. -Plan your scripts accordingly: put anything that must succeed before your code ships in `pre_deploy`. +Put anything that must succeed before your code ships in `pre_deploy`, because only a failing `pre_deploy` script stops the deploy. ::: diff --git a/cloud_docs/reference/scloud-yaml-schema.md b/cloud_docs/reference/scloud-yaml-schema.md index ee2bc1b5..01516ba2 100644 --- a/cloud_docs/reference/scloud-yaml-schema.md +++ b/cloud_docs/reference/scloud-yaml-schema.md @@ -8,7 +8,7 @@ description: "The schema for scloud.yaml: every key, its type, what the Cloud CL A Serverpod project deployed to Serverpod Cloud has a `scloud.yaml` file at its root. The file links the local project to a Cloud project, optionally pins the Dart SDK used for builds, configures how your Flutter app is published, and lists commands to run before or after each deploy. -Two commands write the file: `serverpod cloud launch` creates it on first setup, and `serverpod cloud project link` creates or updates it when you link your codebase to a Cloud project. You can also hand-edit it at any time, and the Cloud CLI preserves your `dartSdk`, app settings, and hook scripts across later commands. See [How the Cloud CLI updates the file](#how-the-cloud-cli-updates-the-file) for the exact per-field rules. +Two commands write the file. `serverpod cloud launch` creates it on first setup, and `serverpod cloud project link` creates or updates it when you link your codebase to a Cloud project. You can also hand-edit it at any time, and the Cloud CLI preserves your `dartSdk`, app settings, and hook scripts across later commands. See [How the Cloud CLI updates the file](#how-the-cloud-cli-updates-the-file) for the exact per-field rules. ## File location