-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rails 7.0.1 and Ruby 3.1.0 #3509
Comments
The major pitfall as of now is that it's incompatible in the gemspec, meaning Refinery won't even bundle install with Rails 7, much less work. Not even the master branch, and as far as I know there's not a draft PR to try to make it work either. Not meaning this as a slight on the devs, who are very nice and smart people. It's just that Refinery development isn't happening at a rapid pace these days. Also, no VIPS. Refinery depends on Dragonfly, which again depends on Imagemagick. In theory, Dragonfly could use Vips; in practice it doesn't (there's an extension to make it work that lacks half the features of the IM version). Also, be aware that not all extensions support the same Rails versions. The page-images extension (which I built my site around) is stuck on Rails 5.1, for instance, meaning it can hold the whole rest of the app back. I'm not a Refinery developer, so I don't know if there's a time frame for supporting Rails 7. There's a lot of moving parts to a CMS, not even Alchemy CMS (which has rapid development) supports Rails 7 yet. A good thing is that since Refinery never tried to migrate to Webpack, they'll probably have a smoother upgrade since Webpacker has been sunset now. :) Not trying to dissuade you from using Refinery, which still has a lot of good things going for it. But you shouldn't expect being on the newest Rails. |
Thanks @evenreven! Appreciate it. |
@mountaindog did you find any alternative to the Refinery? I'm also in the same position where I wanna use it with rails 7+ |
Not necessary an issue, more wondering if anyone has tested Refinery with the latest versions of Rails using importmaps, VIPS and Ruby? Thinking about implementing this CMS into a new Rails project. Love to hear any pitfalls / gotchas, if any.
The text was updated successfully, but these errors were encountered: