Open bignose-debian opened 6 years ago
This isn't really possible without significant development on the Sandstorm platform itself. Sandstorm apps, like this one, operate in a sandbox, and all traffic to and from the sandbox is managed by Sandstorm itself. So either Sandstorm needs to have features added to allow it to connect to grains over SSH, or you need to open up raw IP access to the grain, which only the admin on a Sandstorm server can do, so generally apps shouldn't do.
On 08-Mar-2018, Jacob Weisz wrote:
[…] So either Sandstorm needs to have features added to allow it to connect to grains over SSH, or you need to open up raw IP access to the grain, which only the admin on a Sandstorm server can do, so generally apps shouldn't do.
This seems to imply that the GitWeb grain is not much use on Sandstorm, for intended Git use.
-- \ “Don't you try to outweird me, I get stranger things than you | `\ free with my breakfast cereal.” —Zaphod Beeblebrox, _The | _o_) Restaurant At The End Of The Universe, Douglas Adams | Ben Finney ben@benfinney.id.au
@bignose-debian It works fine, over HTTPS.
It is a conventional best practice, when using Git, to connect over SSH to remote repositories.
Please allow the GitWeb grain to accept a set of SSH public keys, which will allow the Git client to connect to the remote using one of those keys to establish the connection.