Replies: 1 comment
-
Your screenshot indicates you are using a connection profile that restricts the editing of the hostname using Footnotes |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
You have different profiles for each service. This is not needed as you can't really keep up with all the S3-compatible providers out there. Why not let the user simply set the S3 endpoint and region manually? Just have a "Custom S3-compatible Storage"...
For example, I want to use Tigris and I see you have a profile for it named "Globally Distributed S3 Compatibel Object Storage", but it's not using the recommended endpoint to access it outside the Fly.io network which is https://t3.storage.dev. It's using the old one (fly.storage.tigris.dev)
Just let us edit the URL (and possibly a region too) here...

Beta Was this translation helpful? Give feedback.
All reactions