Skip to content
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

capistrano-chewy is holding back chewy version #5

Open
rbq opened this issue Jul 9, 2018 · 2 comments
Open

capistrano-chewy is holding back chewy version #5

rbq opened this issue Jul 9, 2018 · 2 comments
Assignees

Comments

@rbq
Copy link

rbq commented Jul 9, 2018

The chewy Gem recently made a version jump to 5.0.0. Can't use because capistrano-chewy pins it to ~> 0.4.

@nbulaj nbulaj self-assigned this Jul 12, 2018
@nbulaj
Copy link
Owner

nbulaj commented Jul 12, 2018

Hi @rbq . As far as I know Chewy moved forward a lot with it's rake tasks, so I don't sure this gem is currently useful. But let me know if I'm wrong and I need to support this gem.

@rbq
Copy link
Author

rbq commented Jul 13, 2018

Oh, okay, maybe you're right. I got index updates on deployment working again, using the following snippet:

namespace :chewy do
  task :upgrade do
    on roles :app do
      within release_path do
        with rails_env: fetch(:rails_env) do
          execute :rake, 'chewy:parallel:upgrade'
        end
      end
    end
  end
end

after :'deploy:updated',  'chewy:upgrade'
after :'deploy:reverted', 'chewy:upgrade'

Is it actually necessary to wrap each Rake task in a Capistrano one? Or does Cap have a more generic way to invoke Rake tasks on a target host? If this Gem is deprecated, maybe you could add an example to the README?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants