ruby-cff VS Shrine

So the date accessed is the entire year of 2021. It includes the version, at least, but not an actual Git hash, so it really only applies if you use a released version. And then only if they keep their cff file updated, because that isn't actually automatic -- the version is just another field checked in with this file, alongside "date released".

Shrine is great, has more features and a simpler API (imo) than ActiveStorage https://shrinerb.com

Don't you know `carrierwave` and `shrine` work already with this secure way to name folders/files? - https://github.com/carrierwaveuploader/carrierwave - https://github.com/shrinerb/shrine

In general, even though the Hanami ecosystem lacks any "plug-and-play" solutions such as Devise, you can use many existing libraries not tightly coupled to Ruby on Rails. For authentication, you can use Warden, OmniAuth or Rodauth. For uploads there is Shrine. The pagination is built into ROM. Integration with exception catchers such as Rollbar is easy.

Once I knew I wanted to upload images I stated to look around for different ways to do so. I came across a gem named shrine which can be found here https://shrinerb.com/. This is were the hard part came in. Aside from installing the gem like normal, there was a second step that needed to be done to allow images to be rendered. I needed to install https://imagemagick.org/index.php ImageMagick onto my system. After this I was able to add images. ​

A [file field submission](https://github.com/shrinerb/shrine/wiki/Adding-Direct-S3-Uploads) (without Dashboard/Webcam) takes hidden_field :image, value: @photo.cached_image_data and a file_field :image selection in the form, then does this in console when saved:

Toolkit: Shrine