Merge pull request #277 from tigrisdata/copilot/fix-74102481-231e-4583-8c62-196673fee2a0

docs(sdks/s3): fix Fly endpoints to use fly.storage.tigris.dev instead of t3.storage.dev

Author: Xe

.devcontainer/Dockerfile

@@ -1,4 +1,6 @@
 FROM mcr.microsoft.com/devcontainers/base:bookworm
 
 VOLUME /workspace/tigris-os-docs/node_modules
-VOLUME /workspace/tigris-os-docs/.docusaurus
+VOLUME /workspace/tigris-os-docs/.docusaurus
+
+RUN apt-get update && apt-get install -y ffmpeg

docs/sdks/s3/aws-cli.md

@@ -12,7 +12,8 @@ by updating your endpoint URL configuration:
 - IAM requests must be directed to `https://iam.storage.dev`
 - S3 requests made from outside Fly should be directed to
   `https://t3.storage.dev`
-- S3 requests made from within Fly must be directed to `https://t3.storage.dev`
+- S3 requests made from within Fly must be directed to
+  `https://fly.storage.tigris.dev`
 
 When using the AWS CLI, this service endpoint is set by default based on the
 region and is not configured by the user directly. AWS S3 recommends using
@@ -36,7 +37,7 @@ Default output format [None]: json
 
 You can then use the AWS CLI as you normally would, but with the
 `--endpoint-url` flag set to `https://t3.storage.dev` or
-`https://t3.storage.dev`:
+`https://fly.storage.tigris.dev`:
 
 ```bash
 aws s3api list-buckets --endpoint-url https://t3.storage.dev

docs/sdks/s3/aws-elixir-sdk.mdx

@@ -9,7 +9,8 @@ available.
 You may continue to use the ExAWS SDK as you normally would, but with the
 endpoint set to Tigris. If you are using Tigris outside of Fly, use the endpoint
 [https://t3.storage.dev](https://t3.storage.dev). If you are using Tigris from
-within Fly, use the endpoint [https://t3.storage.dev](https://t3.storage.dev).
+within Fly, use the endpoint
+[https://fly.storage.tigris.dev](https://fly.storage.tigris.dev).
 
 This example reads the credentials from the environment variables
 `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.

docs/sdks/s3/aws-go-sdk.mdx

@@ -9,7 +9,8 @@ available.
 You may continue to use the AWS Go SDK as you normally would, but with the
 endpoint set to Tigris. If you are using Tigris outside of Fly, use the endpoint
 [https://t3.storage.dev](https://t3.storage.dev). If you are using Tigris from
-within Fly, use the endpoint [https://t3.storage.dev](https://t3.storage.dev).
+within Fly, use the endpoint
+[https://fly.storage.tigris.dev](https://fly.storage.tigris.dev).
 
 This example uses the [AWS Go SDK v2](https://github.com/aws/aws-sdk-go-v2) and
 reads the default credentials file or the environment variables

docs/sdks/s3/aws-java-sdk.md

@@ -7,7 +7,8 @@ available.
 You may continue to use the AWS Java SDK as you normally would, but with the
 endpoint set to Tigris. If you are using Tigris outside of Fly, use the endpoint
 [https://t3.storage.dev](https://t3.storage.dev). If you are using Tigris from
-within Fly, use the endpoint [https://t3.storage.dev](https://t3.storage.dev).
+within Fly, use the endpoint
+[https://fly.storage.tigris.dev](https://fly.storage.tigris.dev).
 
 This example uses the [AWS Java SDK v2](https://github.com/aws/aws-sdk-java-v2)
 

docs/sdks/s3/aws-js-sdk.mdx

@@ -9,8 +9,9 @@ available.
 You may continue to use the AWS JS SDK as you normally would, but with the
 endpoint set to Tigris. If you are using Tigris outside of Fly, use the endpoint
 [https://t3.storage.dev](https://t3.storage.dev). If you are using Tigris from
-within Fly, use the endpoint [https://t3.storage.dev](https://t3.storage.dev).
-Also make sure that `s3ForcePathStyle` is set to `false`.
+within Fly, use the endpoint
+[https://fly.storage.tigris.dev](https://fly.storage.tigris.dev). Also make sure
+that `s3ForcePathStyle` is set to `false`.
 
 ```js
 import { S3Client } from "@aws-sdk/client-s3";

docs/sdks/s3/aws-net-sdk.mdx

@@ -9,7 +9,8 @@ available.
 You may continue to use the AWS .Net SDK as you normally would, but with the
 endpoint set to Tigris. If you are using Tigris outside of Fly, use the endpoint
 [https://t3.storage.dev](https://t3.storage.dev). If you are using Tigris from
-within Fly, use the endpoint [https://t3.storage.dev](https://t3.storage.dev).
+within Fly, use the endpoint
+[https://fly.storage.tigris.dev](https://fly.storage.tigris.dev).
 
 This example uses the
 [AWS .Net SDK v3](https://www.nuget.org/packages/AWSSDK.S3) and reads the
@@ -28,7 +29,8 @@ dotnet add package AWSSDK.SSOOIDC
 Then you can use the SDK as you normally would, but with the endpoint set to
 Tigris. If you are using Tigris outside of Fly, use the endpoint
 [https://t3.storage.dev](https://t3.storage.dev). If you are using Tigris from
-within Fly, use the endpoint [https://t3.storage.dev](https://t3.storage.dev).
+within Fly, use the endpoint
+[https://fly.storage.tigris.dev](https://fly.storage.tigris.dev).
 
 import gettingStarted from "!!raw-loader!../../../examples/dotnet/GettingStarted.cs";
 

docs/sdks/s3/aws-php-sdk.md

@@ -7,7 +7,8 @@ available.
 You may continue to use the AWS PHP SDK as you normally would, but with the
 endpoint set to Tigris. If you are using Tigris outside of Fly, use the endpoint
 [https://t3.storage.dev](https://t3.storage.dev). If you are using Tigris from
-within Fly, use the endpoint [https://t3.storage.dev](https://t3.storage.dev).
+within Fly, use the endpoint
+[https://fly.storage.tigris.dev](https://fly.storage.tigris.dev).
 
 ## Getting started
 

docs/sdks/s3/aws-python-sdk.mdx

@@ -9,8 +9,9 @@ available.
 You may continue to use the AWS Python SDK as you normally would, but with the
 endpoint set to Tigris. If you are using Tigris outside of Fly, use the endpoint
 [https://t3.storage.dev](https://t3.storage.dev). If you are using Tigris from
-within Fly, use the endpoint [https://t3.storage.dev](https://t3.storage.dev).
-Also ensure that the addressing style is set to `virtual`.
+within Fly, use the endpoint
+[https://fly.storage.tigris.dev](https://fly.storage.tigris.dev). Also ensure
+that the addressing style is set to `virtual`.
 
 ```python
 # Create S3 service client

docs/sdks/s3/aws-ruby-sdk.mdx

@@ -9,8 +9,9 @@ available.
 You may continue to use the AWS Ruby SDK as you normally would, but with the
 endpoint set to Tigris. If you are using Tigris outside of Fly, use the endpoint
 [https://t3.storage.dev](https://t3.storage.dev). If you are using Tigris from
-within Fly, use the endpoint [https://t3.storage.dev](https://t3.storage.dev).
-Also make sure `force_path_style` is set to false:
+within Fly, use the endpoint
+[https://fly.storage.tigris.dev](https://fly.storage.tigris.dev). Also make sure
+`force_path_style` is set to false:
 
 ```ruby
 s3 = Aws::S3::Client.new(
@@ -33,7 +34,8 @@ import Gemfile from "!!raw-loader!../../../examples/ruby/Gemfile";
 Then you can use the SDK as you normally would, but with the endpoint set to
 Tigris. If you are using Tigris outside of Fly, use the endpoint
 [https://t3.storage.dev](https://t3.storage.dev). If you are using Tigris from
-within Fly, use the endpoint [https://t3.storage.dev](https://t3.storage.dev).
+within Fly, use the endpoint
+[https://fly.storage.tigris.dev](https://fly.storage.tigris.dev).
 
 import gettingStarted from "!!raw-loader!../../../examples/ruby/getting_started.rb";