Conor Schaefer

This has been biting me. As a workaround, you can simply run `vagrant destroy -f` a second time to clean up the machine directories. After doing so, running `vagrant up`...

The ideal solution would handle GPG key management in a generalized sense. Unfortunately Ansible doesn't offer a module for gpg keys (as of v2.0.2). The best community module I've found...

> Ubuntu Trusty is now on the 4.4 kernel series itself. Where do you get that information from, @fowlslegs? Running a dist-upgrade on a trusty box tops out at 3.13,...

There is a WIP module in feature branch `parse-cleartext-sigs`; leaving issue open.

Good idea, @huertanix! In practice I've seen knowledgeable users document the 2FA TOTP seed value, to help recovery situations if a phone gets lost. That's not good practice, though, and...

Agreed with @msheiny. The transition from Apache -> Nginx is further complicated by the fact that we don't have a good configuration migration story (#1966). We should be able to...

Sorry, I should have mentioned this, as well: after the initial sync, successive syncs (observed in ~/.lipsync/lipsyncd.log) fail by trying to use rsync over port 22, even though a non-standard...

If I am understanding correctly, the problem may lie in line 48 /bin/lipsync, which reads: rsync -rav --stats --log-file=/home/$USER_NAME/.lipsyncd/lipsyncd.log -e "ssh -l $USER_NAME -p $SSH_PORT" --delete $REMOTE_HOST:$LOCAL_DIR $REMOTE_DIR I believe...

Changing the initial sync order for me worked. I have not yet fixed the subsequent syncs failing due to port 22 being used despite declaration of nonstandard port during setup....

Never did cobble together an implementation to my liking, currently using a hodge-podge of other tools to get the job done. Very interested in your results if you're successful, @mihai-satmarean...