On May 14, 2010, at 9:53 AM, Erich Heine wrote:
Bram,
You've already done the hard part! Assuming you saved the file as mypw.py,
just put an
from mypw import e2
at the top of the fabfile, and you are good to go. Like christian mentioned,
a fabfile is just python, so you can treat
Hi all,
Just a note for anyone who likes to follow master, I've implemented
ticket 151, allowing the output controls to manage user/fabfile level
output:
http://code.fabfile.org/issues/show/151
So you can now replace print() calls in lower level library-like code
with calls to puts(), and
You could also change the passwords, rendering the ones recorded in
history outdated. Whichever method is easier.
On Fri, May 14, 2010 at 3:59 PM, sstein...@gmail.com
sstein...@gmail.com wrote:
Not that it's come up, but don't forget to do a destructive purge on any
history for the file that
On May 14, 2010, at 9:16 PM, Matthew Good wrote:
Changing the passwords is also more secure. Purging them from the repository
history only prevents them from spreading further, but doesn't remove them
from the other hard drives they've already been checked out on.
Yes, the passwords
