I hope it's resize.įor cropping modes, is it always from the center? Are there plans to support other 'gravity' modes? The docs say, 'If only one parameter is specified, the image will be resized and cropped, maintaining the aspect ratio.' I believe that with only one parameter, you could either resize or crop, but not both. The blog post states 'default mode maintains aspect ratio and the resize mode is fill', but the docs say that cover is the default mode. Will the returned image be 675px tall, maintaining the 16×9 aspect ratio I want? However, it's unclear from the docs if one of the most common use cases is supported: requesting an image at a specific aspect ratio while not exceeding a maximum size.įor instance, I want a 1600×900px hero image at the top of my blog posts, but my source image is only 1200px wide. So many of your competitors get it wrong.

In nearly two decades developing for the web, I've never found a good reason to enlarge an image server-side, so thank you for anticipating that footgun. I doubt we'll ever get to a 'build our own datacenter' stage - we'll probably just continue to focus on the application level (with a Database-centric view of the world) There's no shame in that from our POV, and these services deserve the credit for delivering something useful. We are trying to build a great developer platform, and at our current stage these platforms provide a better service for some features than we could ourselves. > Other platforms-as-a-service don't seem to like to acknowledge the services they use under the hood Is this an intentional strategy? Can you talk any more about how you're thinking about it? Portability is something we think about a lot (although harder to solve this problem at a CDN-level). We use Cloudflare right now for the CDN, but as mentioned in the blog post the Webhooks we built into this release are so that we could migrate to any CDN service without locking ourselves into any CDN-specific cache invalidation. Becoming the 'glue' appears to be a byproduct of this approachįor example: we use s3 right now, but we've built the storage server so that it can be extended with other storage providers (in fact, it has a 'local disk' provider for developing locally).

It might be more precise to say that we provide the primitives that a developer needs to host Supabase on any cloud provider.

explicitly targeting being the glue between a bunch of lower level infrastructure

Image resize cdn