Google Cloud Storage for Shrine
MIT License
Bot releases are visible (Hide)
public
option on storage, which enabled the publicRead
default ACL, as an easier way to create public objectsexpires
was not providedPublished by renchap almost 3 years ago
Published by renchap over 3 years ago
Published by renchap over 4 years ago
Published by renchap almost 5 years ago
Published by renchap almost 5 years ago
google-cloud-storage
gem, a workaround has been added so it now works currently (issue #36)Published by renchap over 5 years ago
presign
changed to match the new Shrine signatureclear!
now accepts a block for conditional deletion. If a block is provided, it will only delete the files for which the block evaluates to true
(#31 by @hwo411)presign
has been updated to use the new Shrine 2.11 API. This is a breaking change if you use presign
, and bumps the shrine
dependency to >= 2.11
(#25 by @janko)Shrine.with_file
, introduced in Shrine 2.11 (#29 by @janko)clear!
was potentially not deleting every file (#26 by @janko)Published by renchap over 6 years ago
presign
now correctly returns the headers needed for the PUT
request (#23 by @janko-m)google-cloud-ruby
, which enables credentials discovery#url
now supports presigning (url(expires: …)
), matching the S3 storage (#16 by @rosskevin)google-cloud-storage
gem (#16 by @rosskevin)test/create_test_environment.sh
script to setup a test environment automatically (#16 by @rosskevin)skip_lookup: true
when instanciating a bucket object to avoid an API call. This reduces the number of API calls for most operations, making them faster. It also allows operating on buckets with a restricted Service Account that does not have access to storage.buckets.get
but can access the files. (#21)multi_delete
, as this feature has been deprecated in Shrine