[pass] Password syncronization
Luca Pretto
luca at korneolo.net
Fri Jan 30 13:00:42 CET 2015
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 27/01/15 11:52, George Angelopoulos ha scritto:
> Make a bare git repo so we can *push* to it. No 'bare', no push.
> And we're done on the server. $ mkdir password-store $ cd
> password-store $ git init --bare
>
> Locally: Init the things. $ pass init john at example.com $ pass git
> init
>
> Tell git where the server is, and push the things we initialized. $
> pass git remote add origin
> ssh://john@serverhostname.example.com:/home/john/password-store $
> git push --set-upstream origin master
>
> Set up a git hook that runs every time there is a new commit. This
> hook first fetches any changes we don't have locally, then rebases
> our recent local commit on top of those changes, then sends it all
> back to the server. $ echo git pull --rebase >
> .password-store/.git/hooks/post-commit $ echo git push >>
> .password-store/.git/hooks/post-commit $ chmod u+x
> .password-store/.git/hooks/post-commit
Thanks a lot George: this worked! :-)
But only for 1 "bare" server and 1 client.
Then I'm facing troubles when I try to add other clients (my setup: 2
workstations, 1 laptop, 1 mobile).
On the other clients I run:
$ pass init john at example.com
$ pass git init
$ pass git remote add origin
ssh://john@serverhostname.example.com:/home/john/password-store
$ pass git push --set-upstream origin master
And then I'm stuck with:
[...] the remote contains work that you do not have locally. This is
usually caused by another repository pushing to the same ref [...]
So:
$ pass git pull#merge#commit#fetch#something-wrecking-my-mind? :-D
I don't want to bother you too much: if this is getting too
complicated I'll go back to my old ownCloud/SeaFile solution.
But.. I thought that a pure pass/git setup would have been cool. ;-)
Cheers,
Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJUy3JqAAoJEF+motTmGgbaboIP/R6c8U1E+Ya056UOtC26elZ2
ElZhaNEkbvSMEWDQK2g761Y/5es2uf7upamGqta8PdUKrPmSaGFyrdqglsOIGIut
N+htjFYKGKZiAikmDiJmmShnfMloDW5NVj9c+971MMc38sONfc81vgJ1zjOLveYE
yksfbUAYgEvmM069rQzKYTSghUsyHJMnEteZFItOomBMBD8ICDxFWmmI2Qc/PYji
PP5WM5rK38/xA0rWzPdrjVHLaSfszOLPdCCqk/E0OhgLK858nK5gbS5IiS2rCSeZ
RB0ZA6nHPQUwoiFyTyZV1+xvWEu0wEI9zPCIaU7ktNyuL/pTslOyR/qL84GTSycU
Dy8QL4LZW4BlPKCKyxiPMecjvjncY8Sf6Ee6e7xkX/L0oZ/EUKXswlVzjyrLIs8u
1+7fgD/D7xAcCzeG/xSt8yz/gcoQAvyO7aiuo1JH3HpTeiVwbVNuQeR5O+JOd6ik
A55Y296lxD4L2lbB9L1vT3PFNjDzGIZFO2fM9B8RHgT1POkq1o8VPfhKohyEY80W
AhHEo6jJdn9ZrTWHYsI5JqRpnvba3Fm76zCe/f3Bl8MKoCwQrFQaeW3+qtIMV8K0
sjGWJwMBnA3p62CKVkJoJ2CuvrTm1mOH29XCvKbTULSae0rVIWQtQyqj3HTZDBcr
zalbq9/4IijPUUsfeBU2
=qSp+
-----END PGP SIGNATURE-----
More information about the Password-Store
mailing list