What about a -d/--debug option ?
The DOKKU_TRACE can't be set through ssh.

Also the DOKKU_TRACE should apply in all plugins.
The main dokku script can set the DOKKU_TRACE to avoid do paramaters checking in all plugins

I believe it can be set via SSH. However it won't be set when you do a git
push. Another alternative is to look for a file called DOKKU_TRACE.

And yes, it should apply to plugins, but that is a limitation of the
pluginhook, which still has a number of problems.

On Tue, Oct 29, 2013 at 5:53 PM, Paul Lietar notifications@github.comwrote:

What about a -d option ?
The DOKKU_TRACE can't be set through ssh.
Also the DOKKU_TRACE should apply in all plugins.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/275#issuecomment-27351363
.

Jeff Lindsay
http://progrium.com

How do you set it with SSH ?

How does pluginhook handle stderr ?

pluginhook should handle stderr. But it's been a while since I've looked
at it. It's not that complicated if you want to look.

So normally you could set it in the command you want to remotely execute:

ssh root@server DOKKU_TRACE=true dokku plugins

Which is fine for me. However that won't work with sshcomand and doing
remote dokku commands like this:

ssh dokku@server DOKKU_TRACE=true plugins

Because this would resolve to: /usr/local/bin/dokku DOKKU_TRACE=true plugins

And lastly, if the server allowed it, you can send local vars like this:

DOKKU_TRACE=true ssh -o SendEnv=DOKKU_TRACE dokku@server plugins

And it would work, however by default this is not allowed.

On Tue, Oct 29, 2013 at 5:59 PM, Paul Lietar notifications@github.comwrote:

How do you set it through SSH ?

Does pluginhook handle stderr ?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/275#issuecomment-27351778
.

Jeff Lindsay
http://progrium.com