External cloud storage adapter?

[jacobgranberry]

Hey there! I love what Keystatic is doing, it's perfect for a Wiki site I'd like to build. However, this wiki has a lot of images - over 2GB worth and I'm pretty hesitant to have all of that stored in Github (not even sure the size capacity limit on that). Are there any other plans, or existing alternative ways, to source the image uploader field and image storage from an external source such as S3, Cloudinary, or others?

I'm thinking something similar to the PayloadCMS adapter (https://payloadcms.com/blog/plugin-cloud-storage), where I could just plug in a bucket name and credentials pretty easily

[JedWatson]

Hey @jacobgranberry!

Absolutely, we have plans for this, including for the reasons you mention.

We're currently working on a keystatic cloud platform, and specifically building integrated image hosting on top of Cloudflare Workers, R2, and their image optimisation pipeline.

It will sit somewhere between S3 and Cloudinary in terms of functionality. We'll have integrated image upload and browsing, transformations and optimisation, and images will be served from Cloudflare's CDN (we've seen great performance from our prototype); and we're expecting friendlier pricing than Cloudinary's which has a big jump from free to paid.

The plan is to launch a private preview available by invitation during August, and get some experience running it with a few sites in production before we open it up completely. Technically it will be stable (we'll be using it for some high traffic production websites at Thinkmill) but we want to observe how it goes, make sure we've worked through process like DCMA requests / abuse / etc, and also seeing a couple of months of production traffic will help us understand how the underlying costs scale so we can package that predictably.

The images in the keystatic docs are actually already hosted on a prototype of the service, and here's a preview of the UI we're working on for the library:

We're also going to be looking for feedback from our early users to dial in the workflows and user experience. The longer term benefits to building this as part of Keystatic are that we can do some smart things like understanding where images are referenced in different content branches, and we can build a better experience for editing content than would be practical with a plugin architecture for third-party providers.

If you'd like an invite to the preview when it is ready, we'd love to get you and others from the community here involved. We've been so deep in getting this ready, and excited to share what we've built, that seeing you start this discussion today feels great 🎉

[jacobgranberry]

Hey @JedWatson

This all sounds great, glad y'all are already so far along with this service.

I'd love to stay as cheap as possible, at least for my specific needs - my site is non-commercial, purely donation run and so keeping costs low is important, but letting my users edit/upload images easily is also very important. Definitely happy to pay for a service that could handle a bunch of the upkeep I'd rather not do :)

Would love to have a preview invite when ready, happy to test and provide feedback/bug reports/suggestions. In the meantime I'll be converting my current wiki entries to markdown, and hopefully I can plug in those 1500+ images I have pretty easily when the feature is ready!

[jacobgranberry]

@JedWatson question on this upcoming feature - will there be an API to assist in some bulk upload migrations?

[JedWatson]

@jacobgranberry I've had a chat with the team about it, and we probably won't have a bulk upload API from the outset, but it'll be fairly easy to write a script against the normal API to bulk upload images from a directory.

I'm imagining something that uploads all the images in a folder and then writes a .json file out with the original filenames, and uploaded paths, so you can then handle them however you like.

Happy to jam on this with you, I suspect we'll need it for an internal project anyway so while it won't be first-party supported at the outset we can share the code 🙂

[jacobgranberry]

@JedWatson Cool - thanks for the heads up. Writing a script against normal API shouldn't be a big deal - the .json output seems like it would work very well! Happy to help/give input wherever I can

[snimavat]

Would like to see cloudinary support - mainly for its free plan, which is more thn enough for many of the projects

[bbqchickenrobot]

Any news on this front? Came from a google search and didn't see anything in the official docs being that this thread is over a year old

[rebron1900]

我也想问一下，现在进度如何了？

[gxanshu]

Any updates ?