I've just set up a fly.io account and added my backend repo. My backend uses S3, however fly.io tries to automatically use Tigris. I don't even want to use Tigris, but there is nowhere in the UI to turn it off, and whenever my deployment gets to provisioning Tigris, it fails with the error: unsuccessful command flyctl ext tigris createflyctl ext tigris create.
How can I resolve this?
I have also tried accepting the Tigris ToC just to at least get my app running with Tigris, but I'm stuck in a broken flow where fly tries to use Tigris because I use S3 and I can't configure it and stop it because it isn’t properly deployed for the first time yet.
Any help is appreciated, thanks.
Solution
Hi… Try deploying from the command line with fly launchfly launch; it looks like it will allow you to opt‑out of creating a Tigris bucket, etc.:
In general, the Web UI for launching is still considered experimental (last I heard), and it doesn’t have the full set of knobs, feedback mechanisms, …
A few days ago we added the ability to launch your apps with object storage provided by Tigris configured. This is a unique take on S3’s model as Tigris replicates objects globally to ensure they’re fast for anyone using your app, it works like a CDN and S3 combined. (I digress) How it works If you run fly launch from the command line and t...