You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When debugging issues with droplets, it would be helpful if mentors could ssh in.
It probably makes sense to implement this by putting an ssh key on a shared machine, and having mentors ssh into that machine with their own keys, and then ssh from there to the droplet, rather than ssh'ing directly -- that way, if a mentor joins after a droplet is created, they can still connect to it. There was some discussion of this on the GCI mentors stream.
The text was updated successfully, but these errors were encountered:
If we could find an opensource tool like Akamai's authgate, that'd be great, but AFAICT that doesn't currently exist. (I, and a few other folks in the Zulip community, am familiar with authgate from having worked at Akamai.)
Quoth Tim from the mentors stream " ideally, we'd do a small project to add to zulip.git a tool that one can run to give a given GitHub username SSH access to a droplet, and then we can ask students to run it..."
When debugging issues with droplets, it would be helpful if mentors could ssh in.
It probably makes sense to implement this by putting an ssh key on a shared machine, and having mentors ssh into that machine with their own keys, and then ssh from there to the droplet, rather than ssh'ing directly -- that way, if a mentor joins after a droplet is created, they can still connect to it. There was some discussion of this on the GCI mentors stream.
The text was updated successfully, but these errors were encountered: