docs(cloud): Add a storage concept page - #771
Draft
Isakdl wants to merge 1 commit into
Draft
Conversation
Covers the two default storages, choosing private vs public, registering a storage on the server, adding one in the console, the file browser, deletion, and plan limits. The ServerpodCloudStorage class has not landed in the framework yet, so the two registration snippets carry TODO markers to be replaced with the real class, package, and import before this merges. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N237K5XruApUeGphztg8nc
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.
Adds
cloud_docs/concepts/storage.md, a concept page for Serverpod Cloud storage.It covers the two default storages a new project gets, choosing private vs public, registering a storage on the server, adding one in the console, browsing and uploading files, deletion, and plan limits.
Blockers before this can leave draft
ServerpodCloudStoragedoes not exist yet. The two registration snippets use an invented API,pod.addCloudStorage(await ServerpodCloudStorage.create(storageId: 'private')), and carry TODO markers in HTML comments. The shape deliberately mirrors theNativeGoogleCloudStorage.createblock already in the framework file-uploads page, and takes only a storage id because Cloud already knows the bucket name, region, and visibility. No package or import is named, because there is no basis to guess either. Replace both blocks with the real class before merging.privateandpublicstorages have not shipped. The page states as present tense that every new project starts with both, matching the framework template.showBuckets: !ref.watch(configProvider).isProduction. This should merge with the release that flips it.Buckets,Create bucket, andDelete bucket. These need to match before merge, in one direction or the other.Notes
storageId,session.storage, "Serverpod comes with two default storages").database-backups.mddoes, because the numbers live inproject_capsule_products.dartand drift.scloud deployafter creating a storage. The console Redeploy button re-sends the currently active managed-secret version rather than advancing to the latest, so it does not pick up a new storage. The page avoids naming that button for this reason.🤖 Generated with Claude Code
https://claude.ai/code/session_01N237K5XruApUeGphztg8nc