-
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
Feature proposal: Uploading master.key #231
Comments
Hi @brendon , thanks for asking. I don't use the Rails encrypted secrets feature, so I am not comfortable making this a built in part of capistrano-rails. However if you would like to submit a PR to update the Recommendations section of the README, I will gladly accept it. |
Thanks @mattbrictson. I've done up the PR :) |
yes but why is there a |
Isn't that just a max-timeout? |
My comment was largely for humor given that the PR is ancient. Impressed that you are swinging back around to participate in my snark. :) From old release notes: on :all, in: :sequence, wait: 15 do
# This takes all servers, in sequence and waits 15 seconds between
# each server, this might be perfect if you are afraid about
# overloading a shared resource, or want to defer the asset compilation
# over your cluster owing to worries about load
end This matches the behavior we are seeing. Looks like this is a feature of sshkit when running things in sequence: https://github.com/capistrano/sshkit/blob/master/lib/sshkit/runners/sequential.rb def initialize(hosts, options = nil, &block)
super(hosts, options, &block)
@wait_interval = @options[:wait] || 2
end
def execute
last_host = hosts.pop
hosts.each do |host|
run_backend(host, &block)
sleep wait_interval
end
... Think of the countless seconds spent waiting for keys to slowly deploy! |
Thanks @gurgeous, I bet the
Still doesn't make much sense and I suspect that whoever I got the code off of originally added the Thanks for the heads up! :D I should add, I only have one server so that explains why I never noticed the potential for problems there :) |
Ha! Yeah, we only noticed when we switched from one box to four a few days ago :) |
I currently have the following in my deploy configuration:
I was wondering if you'd be interested in integrating this into the
capistrano-rails
gem? (obviously with more options around whether this should happen or not per if the file actually exists locally.)The text was updated successfully, but these errors were encountered: