Hi there,
great work! I think webistrano is a neat solution. I've got a few suggestions for future features that you can take or leave as you will. This is one of them... :)

Sometimes the deploy fails... and sometimes it sits there spinning endlessly.
(see http://rubyglasses.blogspot.com/2009/12/getting-webistrano-to-deploy-under.html for an example)

It'd be really nice if you could optionally surround the deploy process with a timeout... just in case.

Cheers,
Taryn

When you initiate a deploy it usually runs fine, but sometimes it doesn't even spin up. Usually this is a permissions thing, and the deployment doesn't even really 'start', just sits there endlessly in the 'running' state.

Sorry for pointing a lot at my blog, but if you need an example of this happening:
http://rubyglasses.blogspot.com/2009/12/getting-webistrano-to-deploy-under.html

The issue is that when this happens, you can't cancel the deployment. I'm guessing that because the system doesn't register the deployment as having really 'started' the cancel button doesn't show up. But because the deployment fell over, it'll never stop. The end result is that you can never cancel it and it stays in 'running' forever.

What I found then was while I was continually having to re-test (while fixing the permissions thing) , each time had to break the lock - because officially the deployment hadn't 'finished' even though the deploy process was clearly stillborn :(

Obviously this is an aesthetic issue rather than something that actually stops use - and thus not very high priority at all. But I thought you might want to know of what happens in the pathalogical case. :)

Taryn

It would be really nice if we could configure the default shell that webistrano's recipes run under (just like you can do for capistrano). It'd be even nicer if it just automatically used whatever the config says is correct for the capistrano settings.

Right now the system has a shell hard-coded in app/models/deployment.rb in def deploy_in_background

To fix the main issue that was covered in that blogpost I keep pointing at...
http://rubyglasses.blogspot.com/2009/12/getting-webistrano-to-deploy-under.html

I had to hand-hack the webistrano code to add in the shell-command we needed ('bash --login -c' instead of 'sh -c'). It'd be nice to not have to do that :)

Sorry for spamming you with issues/feature-requests. I thin webistrano is great, and these are all mainly small tweaks that you are quite welcome to completely ignore ;)

Cheers and thanks,
Taryn