It's been two weeks since the public release of Webitrano . Webistrano was downloded nearly 500 times and I got a lot of feedback. People seem to like the concept and having a tool to manage Capistrano deployments through a Web UI.
A lot of people wanted to tie recipes not to projects but to stages, so Webistrano 1.1 will let you do that. Further 1.1 will interpolate strings in Capistrano variables correctly so that you can refer to other variables inside configuration entries.
Also more recent versions of needle/net-ssh will be included so that Webistrano will not blow up if you have newer versions installed.
Apart from this new functionality/bug-fixing the UI got some major enhancements and now looks very promising:
I hope to get 1.1 out of the door shortly after RailsConfEurope here in Berlin. If you are there and have any feedback, I would love to hear it.
Good to see you are able to move fast forward. I’m looking forward to meet at Railsconf. Will you do a speak about webistrano?
If not, how about RejectConf tuesday night?
I’ll be speaking about Amazon S3/EC2. I have to see if there is enough time for me to prepare something for RejectConf.
Once again great work. Would installing trunk be safe right now or should I wait until you release? Also, do you make any changes to the gems’s you hold in /vendor? I’m having some problems with ‘undefined method `call’ for nil:NilClass’ coming from capinstrano.
Please feel free to reply to my email address and delete this post as I realise it’s a bit off topic.
At the moment the trunk is the same as the stable branch. The UI work will be commited soon but I would hold on to the stable version until the release.
Version 1.1 will update all gems in /vendor to their current releases.
I have been using webistrano 1.0 for 3 days now, and it seems to solve and simplify a lot of problems we have deploying a variety of projects into different environments.
The interface is pretty neat now, keep the good work, I really like this project, and expect me to contribute in the near future.
I hope to meet you in Railsconf Europe.
I’ve been using it for a while, and I’m really satisfied. I changed completelly our deploy schema, which now is much simpler and consistent.
I just have a little problem with the comment field. Turns out that ‘comment’ happens to be a reserved word for Oracle, and I had to manually fix it. In my case I’ve changed it for ‘coment’, but I think you should take a look at it and change it in the project.
Looking forward for 1.1
Any ideas about a release date, I’ve put off installing 1.0 in favor of waiting for 1.1 ?
@robl:
In the next couple of hours or tomorrow. We are working on the last minor UI fixes and prepare the project homepage.
@Sandro:
This seems to be a Rails issue with table column quoting. I will see if this is fixed with the latest edge.
Thanks dude :)
Duncan, did you ever have any luck fixing that error? I’m having the same problems :-(
Other than that, love Webistrano – thanks for the hard work!
There is a bug with the use of sudo, I’m not sure right now if it is Capistrano or Webistrano but a workaround is this small patch to vendor/plugins/capistrano-2.0.0/lib/capistrano/configuration/actions/invocation.rb on line 94:
- fallback.call(ch, stream, out) + fallback.call(ch, stream, out) unless out.nil? || out.strip.empty?
to follow up on the invocation.rb:
I had to change mine a little different. Somehow fallback was always nil when I was restarting my mongrel. Here’s what I used instead.
(fallback.call(ch, stream, out) + fallback.call(ch, stream, out)) unless fallback.nil? || out.strip.empty?
@Matt:
The commited solution is in trunk:
http://labs.peritor.com/webistrano/changeset/6
I’ve been having the same error as brad and Duncan. Will http://labs.peritor.com/webistrano/changeset/6 be folded into a 1.1.1 release? It doesn’t seem to be in the current 1.1.
I will release a new version in the next days.