-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Migration to Dragonfly ~> 1.0.0. #2500
Conversation
self.dragonfly_url_format = '/system/images/:job/:basename.:ext' | ||
self.dragonfly_url_host = '' | ||
self.trust_file_extensions = false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe deprecation will be better to avoid error raising?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is 3.0 so it's not that much of a problem. Everyone who is using this is on the edge, so... it depends.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's pain to migrate every refinery version to another refinery version. Let's start keeping it less painful and more friendly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, that sounds good. So, Refinery.deprecate
it is?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup. I'll change that later. 😴
I made few updates. I left it in separeted commit for easy review. I'll fixup this before merging. |
Is this ready to go, in your opinion? |
Not yet. I need to test it. |
@parndt I'm getting some issues with refinery-acts-as-indexed master. Bundler can't resolve deps. :( So I can't test it. |
@simi I'll take a look |
☕ for you. |
I get no issues with bundling your fork/branch, but maybe try a) rebasing this pull request against the current refinery/refinerycms and b) get the latest commits to refinery/refinerycms-acts-as-indexed@aa7862f then run |
Shame on me. I was using old |
Hmm, are getting this also? I pointed to this branch (both, testing and refinerycms)
diff --git a/Gemfile b/Gemfile
index 71beeb5..6713051 100644
--- a/Gemfile
+++ b/Gemfile
@@ -2,13 +2,12 @@ source 'https://rubygems.org'
gemspec
-git 'git://github.com/refinery/refinerycms.git', :branch => 'master' do
- gem 'refinerycms'
+gem 'refinerycms', path: '../refinerycms'
- group :development, :test do
- gem 'refinerycms-testing'
- end
+group :development, :test do
+ gem 'refinerycms-testing', path: '../refinerycms'
end
+
gem 'refinerycms-i18n', github: 'refinery/refinerycms-i18n', branch: 'master'
gem 'mime-types', '~> 1.16'
|
Yeah, that's due to old code. I'm currently fixing this, or trying! |
OK, let's go thru CI and I'll rebase into one commit. It will be ok to merge in master, but please don't release yet. I tested acts-as-indexed, so it works as before. |
@parndt 🍏 |
@simi I merged your CI pull request |
@parndt so? |
@simi I'm happy but the PR is saying it cannot be automatically merged. Can you rebase the branch please? |
Migration to Dragonfly ~> 1.0.0.
Thank you!!!!!! |
What wasn't tested:
acts_as_indexed
integrationpingie @ugisozols @parndt