dyross/play-capistrano — comment on commit 97154f1c9ea0d7d276875b2f0c92fd6ac40ecdc8
File:  line 0
By mandubian:

On Thu, Jan 5, 2012 at 11:21 PM, David Y. Ross <
reply@reply.github.com
> wrote:

> Perhaps this is true, but the task doesn't exist with the deploy.rb and
> play_recipes.rb that this module gives. This patch SHOULD make "cap
> play:logs" work out of the box. Otherwise, more changes are needed.
>
>
Isn't "cap setup" a default command from capistrano ? We don't need to
redefine it in our recipes.
But yet, I agree that if there is a problem with this, we must correct it!!!

> Can you check on your apps that use capistrano? Can you see if "cap
> play:logs" works?
>
>
Apparently it works on my hypertrout deployment. Here are the logs.

> cap play:logs
* executing `play:logs'
* executing "tail -f /opt/play/shared/log/hypertrout.log"
servers: ["87.98.167.34"]
Password:
[87.98.167.34] executing command

87.98.167.34: 01:14:10,897 INFO ~ loading
http://api.klout.com/1/users/show.json?key=bfs2g93vm5dn7qr72ju7baxq&users=tonyubot
01:14:11,206 INFO ~ loading
http://api.klout.com/1/soi/influenced_by.json?key=bfs2g93vm5dn7qr72ju7baxq&users=ffmercatino
01:14:11,457 INFO ~ loading
http://api.klout.com/1/soi/influencer_of.json?key=bfs2g93vm5dn7qr72ju7baxq&users=ffmercatino

Pascal

> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/dyross/play-capistrano/commit/97154f1c9ea0d7d276875b2f0c92fd6ac40ecdc8#commitcomment-841878
>