Repository navigation
Add Neon to S3-compatible providers in Amazon S3 provider documentation - #3593
Open
rishi-raj-jain wants to merge 1 commit into
Open
rishi-raj-jain wants to merge 1 commit into
rishi-raj-jain wants to merge 1 commit into
Conversation
|
|
github-actions
Bot
added
contribution
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully 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
2 participants
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.
Description
Preview: https://documentation-git-fork-rishi-raj-jain-main-strapijs.vercel.app/cms/configurations/media-library-providers/amazon-s3#neon
This adds Neon Object Storage to the S3-compatible services section of the Amazon S3 provider page. It works with the existing
aws-s3provider, so the change is a row in the compatibility table, a mention in the TL;DR, and a short config example modeled on the Cloudflare R2 and Tigris ones.Tested on a live Neon project with
@strapi/provider-upload-aws-s35.58.0 and a Strapi 5.58.0 app:ACL: undefined): upload of the original image and generated formats, anonymous reads, Media Library thumbnails, and deletion.ACL: 'private'): stored URLs return 403 and the signed URLs returned by Strapi return 200.ACLreproduces the501 Not Implementederror.uploadStreamwork withforcePathStyle: true.yarn buildpasses locally.Happy to adjust anything!
Disclosure: I work as a contractor at Neon.
Related issue(s)/PR(s)
Follows the same pattern as #3426 (Tigris).