Skip to content

docs: Correct where .scloudignore rules apply and what a deploy uploads - #941

Open
developerjamiu wants to merge 1 commit into
mainfrom
docs/cloud-scloudignore
Open

developerjamiu wants to merge 1 commit into
mainfrom
docs/cloud-scloudignore

Conversation

@developerjamiu

Copy link
Copy Markdown
Contributor

Corrects how the Cloud docs describe what a deploy uploads and where .scloudignore rules apply. In a Serverpod 4 project, the old wording sent readers to the wrong .scloudignore, and files went missing from deploys.

  • Deployments, "Configure what's included": says what a deploy uploads (the server project, the workspace packages it depends on, and the workspace's root pubspec.yaml and pubspec.lock, but not the Flutter app) and what it leaves out. It explains that the CLI creates a .scloudignore in the server project and one in the workspace root, that patterns with a leading or middle / are relative to their file's folder, and that a ! rule must sit in the same folder as the .gitignore it overrides, or below it. The example block is unchanged apart from its title, my_project_server/.scloudignore, since the examples only work there.
  • Ship non-Dart files: assets/ goes in the server project, and Cloud zips the server project, not the whole project directory.
  • project CLI intro: names where the link command creates .scloudignore.

Checked against the Cloud CLI 1.4.0 ignore engine on a Serverpod 4.1.2 project tree with the CLI's own .scloudignore templates.

@developerjamiu developerjamiu self-assigned this Nov 20, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant