On Wed, Dec 4, 2013 at 10:50 AM, Nate Finch <[email protected]> wrote: > Yeah, that's a good point. The problem comes when they don't have putty, or > if they do, we don't know where it is (putty isn't an installed application, > it's a standalone exe, so it can live anywhere... Mine always just lived in > my downloads folder). I'm not sure what the best solution for that is. > There's a bunch of not great work around.
If we can make the restriction that it must live in %PATH% that sounds preferable to a. writing our own ssh client b. adding another configuration value to environments.yaml, especially as that file has no concept of global configuration, only per environment configuration. > > On Dec 3, 2013 6:44 PM, "David Cheney" <[email protected]> wrote: >> >> :) Nice. >> >> The big problem with using the go ssh client is not the ssh support, >> but the terminal handling. To work properly on the remote side you >> need to request a PTY when setting up the shell session. That causes >> the remote shell to send lots of advanced messages, like 'how wide is >> your screen', etc, which need to be handled or you just get poop on >> your screen. Interfacing that with the W32 console subsystem sounds >> like a major headache. >> >> I think for the windows cli the best experience would be to fire off >> putty.exe, so the user has all their normal putty customization >> necessary and doesn't have to use ssh though the crippled win32 >> console. >> >> Cheers >> >> Dave >> >> >> On Wed, Dec 4, 2013 at 10:40 AM, Nate Finch <[email protected]> >> wrote: >> > I wonder if anyone has written an ssh client for go... >> > >> > On Dec 3, 2013 6:10 PM, "David Cheney" <[email protected]> >> > wrote: >> >> >> >> I *think* the putty cli command is something like pssh, we can look it >> >> up. I think this is pretty easy to attempt as we can detect when the >> >> user is running windows and use an alternative command invocation. >> >> >> >> Who wants to raise the issue ? >> >> >> >> On Wed, Dec 4, 2013 at 8:10 AM, Marco Ceppi <[email protected]> wrote: >> >> > We have docs on creating keys for windows users, but not on how to >> >> > set >> >> > up >> >> > PuTTY https://juju.ubuntu.com/docs/getting-started-keygen-win.html We >> >> > should >> >> > probably expand these to installing PuTTY >> >> > >> >> > >> >> > On Tue, Dec 3, 2013 at 3:26 PM, Tim Penhey <[email protected]> >> >> > wrote: >> >> >> >> >> >> Hi folks, >> >> >> >> >> >> I watch the Ask Ubuntu questions around Juju, and saw one yesterday >> >> >> that >> >> >> I think we need to get better docs around. >> >> >> >> >> >> The user was saying he couldn't edit the files on the machines that >> >> >> Juju >> >> >> started. This had me going "huh?". >> >> >> >> >> >> I should have twigged immediately at the use of Filezilla, but it >> >> >> became >> >> >> obvious when someone else suggested just using 'juju ssh' and the >> >> >> error >> >> >> was that 'juju not found in %PATH%'. >> >> >> >> >> >> Do we have docs that help people set up PuTTY on windows, enabling >> >> >> it >> >> >> for juju, and making sure that the key is uploaded? >> >> >> >> >> >> Cheers, >> >> >> Tim >> >> >> >> >> >> -- >> >> >> Juju mailing list >> >> >> [email protected] >> >> >> Modify settings or unsubscribe at: >> >> >> https://lists.ubuntu.com/mailman/listinfo/juju >> >> > >> >> > >> >> > >> >> > -- >> >> > Juju mailing list >> >> > [email protected] >> >> > Modify settings or unsubscribe at: >> >> > https://lists.ubuntu.com/mailman/listinfo/juju >> >> > >> >> >> >> -- >> >> Juju mailing list >> >> [email protected] >> >> Modify settings or unsubscribe at: >> >> https://lists.ubuntu.com/mailman/listinfo/juju -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
