docs: add usage patterns skeleton

Signed-off-by: Xe Iaso <[email protected]>

Author: Xe

docs/blueprints/geesefs-linux.mdx

@@ -0,0 +1,113 @@
+# Mount a Tigris bucket with geesefs
+
+[geesefs](https://github.com/yandex-cloud/geesefs) lets you mount S3 buckets to
+your local Linux system. This tool works with Tigris too, letting you mount any
+Tigris bucket as if it was a normal Linux filesystem.
+
+- Install geesefs
+- Configure credentials
+- systemd service to start geesefs on boot
+- Reboot test
+
+Prerequisites:
+
+- A Tigris account
+- A bucket you want to mount into your system (`mybucket`)
+- A target location you want to mount your bucket to (`~/data`)
+
+:::note
+
+geesefs uses
+[FUSE](https://www.kernel.org/doc/html/latest/filesystems/fuse.html) to mount
+buckets into the filesystem. FUSE has limitations involving multiple users
+accessing the same mountpoint. If you need multiple users (human or service) to
+access the same bucket, consider creating multiple systemd services mounting the
+bucket in each user's home directory.
+
+:::
+
+## Installing geesefs
+
+Download the latest release for your machine from
+[the list of geesefs releases](https://github.com/yandex-cloud/geesefs/releases)
+to `/usr/local/bin`:
+
+<details>
+<summary>amd64 Linux</summary>
+
+```text
+sudo wget -O /usr/local/bin/geesefs https://github.com/yandex-cloud/geesefs/releases/download/v0.42.0/geesefs-linux-amd64
+```
+
+</details>
+<details>
+<summary>arm64/aarch64 Linux</summary>
+
+```text
+sudo wget -O /usr/local/bin/geesefs https://github.com/yandex-cloud/geesefs/releases/download/v0.42.0/geesefs-linux-arm64
+```
+
+</details>
+
+Then mark it as executable:
+
+```
+sudo chmod +x /usr/local/bin/geesefs
+```
+
+## Configure credentials
+
+Create a new access key with edit permissions on your target bucket. Edit
+`~/.aws/credentials` with a text editor:
+
+```
+[default]
+aws_access_key_id = <paste access key starting with tid_>
+aws_secret_access_key = <paste secret access key starting with tsec_>
+```
+
+## Mount bucket on login with systemd
+
+Make a folder for the geesefs service:
+
+```text
+mkdir -p ~/.local/share/systemd/user
+```
+
+Then copy this unit into `~/.local/share/systemd/user/mount-data.service`:
+
+```text
+[Unit]
+Description=Mount Tigris bucket mybucket to ~/data
+After=network.target
+
+[Service]
+Type=forking
+WorkingDirectory=%h
+ExecStart=/usr/local/bin/geesefs --endpoint https://fly.storage.tigris.dev mybucket %h/data
+
+[Install]
+WantedBy=default.target
+```
+
+Make sure to adjust `mybucket` and `%h/data` as needed. In systemd units, `%h`
+refers to your home directory, so this mounts bucket `mybucket` to `~/data`.
+
+Enable the unit with `systemctl daemon-reload` and `systemctl enable`:
+
+```text
+systemctl --user daemon-reload
+systemctl --user enable --now mount-data.service
+```
+
+## Reboot test
+
+Reboot your system and log back in. Run the mount command and you should see
+information about geesefs mounting your bucket:
+
+```text
+$ mount | grep geesefs
+mybucket on /home/opc/data type fuse.geesefs (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,default_permissions)
+```
+
+You did it!

docs/usage-patterns/index.md

@@ -0,0 +1,30 @@
+# Usage patterns
+
+Tigris gives you globally distributed object storage so that your data loads
+fast anywhere on the planet. Here are the patterns that let you use Tigris the
+best ways.
+
+## Run compute anywhere
+
+If you put your language models, docker images, or other weights in Tigris, they
+download fast everywhere on the planet. This means you can put serverless
+compute near your users without having to waste time waiting for things to
+download. There's no need to waste money maintaining local storage for your
+weights when they download in seconds.
+
+## Global distribution
+
+Tigris is a CDN out of the box. If your users upload images in Seattle, their
+friends in Seattle grab the images from Seattle. No need to funnel everything
+through Northern Virginia or configure bucket replication rules. When you create
+artifacts from your AI models in Tigris, they're always close to your users so
+they load as fast as possible. There's no need to make a new CDN config when
+your storage system is your CDN!
+
+## Multi-cloud native
+
+Configure a bucket with [shadow bucket replication](/docs/migration/) and all
+your data is upgraded into Tigris on demand. Configure off-site backups with any
+tool that works with S3. Mount your buckets into your Kubernetes workloads with
+[csi-s3](https://github.com/yandex-cloud/k8s-csi-s3) or into your Linux systems
+with [geesefs](/docs/blueprints/geesefs-linux).

sidebars.js

@@ -106,10 +106,15 @@ const sidebars = {
         "sdks/s3/aws-net-sdk",
       ],
     },
+    {
+      type: "category",
+      label: "Usage patterns",
+      items: ["usage-patterns/index"],
+    },
     {
       type: "category",
       label: "Blueprints",
-      items: ["blueprints/docker-registry"],
+      items: ["blueprints/docker-registry", "blueprints/geesefs-linux"],
     },
     {
       type: "doc",