Change Maglev CMS uploader (asset management) to use Shrine instead of Active Storage.
Add the gem to your Gemfile and run bundle install:
gem 'maglevcms-shrine'
Generate migration, run migrations and add a new initializer to configure the gem:
bundle exec rails g maglev:shrine:instal
No changes are required from the application side. The gem takes care of doing all the necessary changes so Maglev starts using Shrine.
NOTE: Active Storage needs to still be loaded in the application because app/controllers/maglev/api/assets_controller.rb in the maglev-core gem uses it.
After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and the created tag, and push the .gem file to rubygems.org.
FAQs
Unknown package
We found that maglevcms-shrine demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.