Closed mtarsi closed 10 years ago
If you kill dandelion w/ ctrl+c do you get a stack trace printed in your terminal?
I do, this is what I get:
^C/Library/Ruby/Gems/2.0.0/gems/net-ssh-2.7.0/lib/net/ssh/ruby_compat.rb:30:in `select': Interrupt
from /Library/Ruby/Gems/2.0.0/gems/net-ssh-2.7.0/lib/net/ssh/ruby_compat.rb:30:in `io_select'
from /Library/Ruby/Gems/2.0.0/gems/net-ssh-2.7.0/lib/net/ssh/connection/session.rb:209:in `process'
from /Library/Ruby/Gems/2.0.0/gems/net-ssh-2.7.0/lib/net/ssh/connection/session.rb:169:in `block in loop'
from /Library/Ruby/Gems/2.0.0/gems/net-ssh-2.7.0/lib/net/ssh/connection/session.rb:169:in `loop'
from /Library/Ruby/Gems/2.0.0/gems/net-ssh-2.7.0/lib/net/ssh/connection/session.rb:169:in `loop'
from /Library/Ruby/Gems/2.0.0/gems/net-sftp-2.1.2/lib/net/sftp/session.rb:802:in `loop'
from /Library/Ruby/Gems/2.0.0/gems/net-sftp-2.1.2/lib/net/sftp/operations/upload.rb:203:in `wait'
from /Library/Ruby/Gems/2.0.0/gems/net-sftp-2.1.2/lib/net/sftp/session.rb:103:in `upload!'
from /Library/Ruby/Gems/2.0.0/gems/dandelion-0.3.14/lib/dandelion/backend/sftp.rb:34:in `block in write'
from /Library/Ruby/Gems/2.0.0/gems/dandelion-0.3.14/lib/dandelion/backend.rb:49:in `temp'
from /Library/Ruby/Gems/2.0.0/gems/dandelion-0.3.14/lib/dandelion/backend/sftp.rb:32:in `write'
from /Library/Ruby/Gems/2.0.0/gems/dandelion-0.3.14/lib/dandelion/deployment.rb:156:in `block in deploy'
from /Library/Ruby/Gems/2.0.0/gems/dandelion-0.3.14/lib/dandelion/deployment.rb:150:in `each'
from /Library/Ruby/Gems/2.0.0/gems/dandelion-0.3.14/lib/dandelion/deployment.rb:150:in `deploy'
from /Library/Ruby/Gems/2.0.0/gems/dandelion-0.3.14/lib/dandelion/command/deploy.rb:50:in `execute'
from /Library/Ruby/Gems/2.0.0/gems/dandelion-0.3.14/lib/dandelion/application.rb:38:in `block in execute'
from /Library/Ruby/Gems/2.0.0/gems/dandelion-0.3.14/lib/dandelion/command.rb:92:in `initialize'
from /Library/Ruby/Gems/2.0.0/gems/dandelion-0.3.14/lib/dandelion/application.rb:36:in `new'
from /Library/Ruby/Gems/2.0.0/gems/dandelion-0.3.14/lib/dandelion/application.rb:36:in `execute'
from /Library/Ruby/Gems/2.0.0/gems/dandelion-0.3.14/lib/dandelion/application.rb:7:in `execute'
from /Library/Ruby/Gems/2.0.0/gems/dandelion-0.3.14/bin/dandelion:7:in `<top (required)>'
from /usr/bin/dandelion:23:in `load'
from /usr/bin/dandelion:23:in `<main>'
It appears that it might just be an issue with GoDaddy. I was able to transfer the site via traditional ftp. It did slow down half way through the transfer with Transmit but it was able to finish the transfer.
I added a revision file and now I can deploy incremental changes.
Not sure if there is something dandelion could do with throttling?
@mtarsi Did you try uploading via FTP with Dandelion as well or just Transmit?
I'm deploying a repository to GoDaddy. I have my config file setup correctly as the deployment works for roughly 5 minutes and then the transfer log appears to timeout or go idle. Is there a setting I'm missing in my configuration?