Azure storage adapter

Hey @janko!

I really love using shrine.rb on my ruby projects.

One of my clients requires Azure Storage and I was thinking about helping/contributing to the codebase by implement an official storage adapter for it, following the discussion here: .

I used the same approach like here on one of my projects and it seems to work fine.

What do you say?


Hi Robi, I’m happy to hear Shrine is working well for you :heart:

Yes, I would love to have an official Azure storage. The closest we currently have is this gem, which seems to provide a decent implementation, with some additional GC massaging. I don’t know how complete it is, but it’s not ideal that the gem is currently named shrine-storage :stuck_out_tongue: Maybe it would make sense to try to collaborate with them on this gem, you can be the judge of that.

Regardless of whether you decide to create a new gem or collaborate on shrine-storage, you can choose whether you’d prefer to publish it on the shrinerb organization (I could provide permissions), or you’d prefer to have it on your account and we could link to it from the Shrine docs.

1 Like

Sounds like a plan! I will let you know what I decided after I have a better look.

Hi there,

i think i stumbled upon via this post and as i need azure as a storage i tried using it. Found that somehow the current gem didn’t work at all and using the latest from git worked somewhat but had an issue with mime_types not being set.

Also it currently completely lacks support for signed urls and using public storage containers on azure is an absolute no-go for my requirements.

As the latest version of the gem depends on the azure libs version 1.0 and there is already a 2.0 i extracted the main storage adapter and started to implement support for SAS signing the urls.

As the person or organization who created the the shrine-storage gem neither replied to your question from like weeks ago and hasn’t reacted to my small PR about the mime_type either i decided to take the main part and start to integrate it into a shrine fork.

Or would this be better suited to be an extra gem still?

Got a first working version where i added signed URL support, original gem only supported public readable containers.

1 Like