-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom URL for S3 compatible services #2
Comments
Thank you for bringing issues to our attention! |
Supporting custom storage providers is a great idea for the template. However, my approach with this template has been to provide a fully functional and opinionated setup rather than adding multiple configuration options. When building it, I found that having too many choices made it harder to maintain a simple starting point. That said, if there's enough interest, we could consider adding an alternative version that supports an AWS_S3_URL environment variable to override the default AWS endpoint. This should work with providers that follow the S3 API standard. A few things that come to mind:
Are you planing on testing these changes? If so, which providers are you planning to use? I'd be happy to hear your findings and see if it makes sense to include an alternative version. I don't want to turn away from these types of collaborations, but I do want to still provide a full working template that is made to plug and play. What I would like to do is have multiple versions of this template that has different options, but is fully functional. I believe that will be the most beneficial for startups. |
S3 Bucket to be used from other S3 compatible services.
Could be added to ENV file an AWS_S3_URL and also that to be customizable, to use for example Cloudflare, Minio, Hetzner File system (or other)?
like this, just I cannot test yet cause I am on localhost now.
const s3Client = new S3Client({
region: process.env.AWS_S3_REGION,
endpoint: process.env.AWS_S3_URL,
credentials: {
accessKeyId: process.env.AWS_S3_IAM_ACCESS_KEY!,
secretAccessKey: process.env.AWS_S3_IAM_SECRET_KEY!,
},
forcePathStyle: true,
});
AWS_S3_URL=https://cc6db1e5fb4e.eu.r2.cloudflarestorage.com
The text was updated successfully, but these errors were encountered: