Post: migrating from S3 to branch-aware storage (Neon Storage #4)#1441
Open
bobbyonmagic wants to merge 4 commits into
Open
Post: migrating from S3 to branch-aware storage (Neon Storage #4)#1441bobbyonmagic wants to merge 4 commits into
bobbyonmagic wants to merge 4 commits into
Conversation
Deploying devops-daily with
|
| Latest commit: |
a87fc9d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://37cde918.devops-daily.pages.dev |
| Branch Preview URL: | https://post-neon-migrating-from-s3.devops-daily.pages.dev |
bobbyonmagic
force-pushed
the
post/neon-migrating-from-s3-to-branch-aware-storage
branch
from
d82c905 to
a87fc9d
Compare
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
1 participant
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.
Fourth and final storage post (dated Jul 10). A practical migration guide: Neon storage is S3-compatible, so it's a config change plus a copy loop, not a rewrite.
Covers what stays identical (the S3 SDK calls), the exact client-config diff (endpoint, pinned region, path-style, bucket declared in neon.ts, injected per-branch creds), a list-and-copy migration script, and an honest table of S3 platform features that don't carry over (events, storage classes, cross-region replication). The Neon-write side of the copy loop is the tested path from the demo. Reuses neon-storage-demo.
Interactive: a tabbed same-code/two-configs comparison, the migration script, a warning callout on URL-vs-key storage, a carries-over table, and a github card. OG generated, validated.