Hi Tomasz, On Mon, Sep 19, 2011 at 11:46 AM, Tomasz Melcer <[email protected]> wrote:
> 1. I often use chroot for testing. Are there any helpers planned to make > using chroot easier? Fabric executes a new shell session for each run/sudo -- thus "stateful" things like chroot have to be faked. For example, 'cd' is implemented as a context manager slapping an implicit "cd directory &&" in front of commands. If chroot can be supported in this way (and it seems it can, by 'chroot <command>'?) then we might accept a pull request to add a chroot context manager. > 2. Pipe from remote command to local file. Is it possible to reproduce this > in fabric? That depends a lot on Paramiko's support for it; it could be impossible or very tricky. Sounds like the inverse of https://github.com/fabric/fabric/issues/289. With the current implementation, your best bet is probably to use a temporary on-disk file, or a ramdisk if that's worth the effort to avoid hitting disk. > 3. Is any work done on [1] ("Make use of ssh_config where possible")? I > cannot find the branch mentioned in the last comment. That's probably https://github.com/goosemo/fabric/tree/3-ssh-config , but Morgan can probably confirm/deny. That branch is likely a little out of date now too. Regardless, the ssh_config stuff is a moderately high priority so it'll probably be included in one of the upcoming (post-1.3) releases. Note from that ticket that Paramiko is a limiting factor here too -- just because one can read in values from ssh_config doesn't mean all of ssh's functionality works yet, so some options may be no-ops in Fabric. That said, the basic stuff like host aliases and such is possible to support and would be a good first step. Best, Jeff -- Jeff Forcier Unix sysadmin; Python/Ruby engineer http://bitprophet.org _______________________________________________ Fab-user mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/fab-user
