Repository navigation
docs: Correct where .scloudignore rules apply and what a deploy uploads - #941
Open
developerjamiu wants to merge 1 commit into
Open
developerjamiu wants to merge 1 commit into
developerjamiu wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Corrects how the Cloud docs describe what a deploy uploads and where
.scloudignorerules apply. In a Serverpod 4 project, the old wording sent readers to the wrong.scloudignore, and files went missing from deploys.pubspec.yamlandpubspec.lock, but not the Flutter app) and what it leaves out. It explains that the CLI creates a.scloudignorein 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.gitignoreit overrides, or below it. The example block is unchanged apart from its title,my_project_server/.scloudignore, since the examples only work there.assets/goes in the server project, and Cloud zips the server project, not the whole project directory.projectCLI 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
.scloudignoretemplates.