sudo: no tty present and no askpass program specified about gitreceive HOT 7 CLOSED

I think that's because you aren't provide a user to ssh, so it would normally prompt you for one, but because it's not an interactive terminal, it can't. So you have to provide your programs with enough information or with the right options so they don't need to ask for input like that.

from gitreceive.

sorry, it was hidden because I accidentally used < and >. The issue is that it wants to ask for sudo password, but can't. I just wanted to point this out because this command is in the main readme.

from gitreceive.

Oh I see! Yes, that's problematic.

from gitreceive.

Hmm; I can't think of a good way to fix this - I don't encounter this as I'm using passwordless sudo. Perhaps we could document around it or encourage use of a user with access to ~git/.ssh/authorized_keys?

from gitreceive.

Maybe the init command can ensure authorized_keys gives global write permissions?

from gitreceive.

In the context of dokku any user on the system is able to manipulate containers using docker so I can't see a downside right now to adding global write to ~git/.ssh/authorized_keys.

We would also have to update documentation across the repositories by removing the sudo or ssh root@ recommendation for the upload-key sub-command.

from gitreceive.

ah, thanks for the quick responses everyone!

from gitreceive.