-
Notifications
You must be signed in to change notification settings - Fork 269
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
Restore manifest is failing on rollback on multiple hosts #204
Comments
Hi! Thanks for the bug report. Is this still a problem for you? I am looking at the source code you referenced (see below), and it seems to me that manifest detection happens inside the rails/lib/capistrano/tasks/assets.rake Lines 88 to 102 in 0a65584
|
Probably this problem is similar to the one I just had, due to |
I have an issue during rollback on multiple host setup with restoring assets manifest. Currently restoring manifest works like this. It checks manifest name in
assets_manifest_backup
dir on one host and then uses this name to check again (assets.rake#L93) on each host if this manifest exists before copying archived manifest topublic/assets
dir.This strategy fails when each host have different manifest (I know it's very unusual) and throws
Capistrano::FileNotFound
error (assets.rake#L98).I propose we should detect manifest name per host.
System configuration
Ruby 2.4.1
capistrano (3.8.2)
capistrano-bundler (1.2.0)
capistrano-passenger (0.2.0)
capistrano-rails (1.2.3)
rails (4.2.9)
rails-deprecated_sanitizer (1.0.3)
rails-dom-testing (1.0.8)
rails-html-sanitizer (1.0.3)
rake (12.0.0)
rspec-rails (3.6.0)
rvm1-capistrano3 (1.4.0)
sass-rails (5.0.6)
sequel-rails (0.9.17)
sprockets-rails (3.2.0)
The text was updated successfully, but these errors were encountered: