<div dir="ltr">I'm using <a href="https://github.com/spwhitton/git-remote-gcrypt">git-remote-gcrypt</a> with a simple bare remote repo in Dropbox. Because the entire remote repo (e.g. including the Git internal objects) are encrypted, neither the file paths nor the Git history should be readable via the remote repo in Dropbox.</div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 4, 2016 at 5:00 PM, Jacob MacDonald <span dir="ltr"><<a href="mailto:jaccarmac@gmail.com" target="_blank">jaccarmac@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class="">> <span style="color:rgb(33,33,33)">Warning: doing "git push" to a non-bare repository is generally not </span><span style="color:rgb(33,33,33)">recommended</span><div><span style="color:rgb(33,33,33)"><br></span></div></span><div><span style="color:rgb(33,33,33)">Very true, my mistake for not being specific here. I do indeed use receive.denyCurrentBranch and it works like a charm.</span></div><div><span style="color:rgb(33,33,33)"><br></span></div><div><span style="color:rgb(33,33,33)">Thanks for the clarification.</span></div></div><div class="HOEnZb"><div class="h5"><br><div class="gmail_quote"><div dir="ltr">On Sun, Dec 4, 2016 at 2:57 PM Brian Candler <<a href="mailto:b.candler@pobox.com" target="_blank">b.candler@pobox.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 04/12/2016 21:26, Jacob MacDonald wrote:<br class="m_-966806696353180239gmail_msg">
> The repository is not stored as bare; That way I can access the files<br class="m_-966806696353180239gmail_msg">
> in the repository directly from Drive<br class="m_-966806696353180239gmail_msg">
<br class="m_-966806696353180239gmail_msg">
Warning: doing "git push" to a non-bare repository is generally not<br class="m_-966806696353180239gmail_msg">
recommended, although you can do it with a post-update hook, or you can<br class="m_-966806696353180239gmail_msg">
use a feature introduced in git 2.3 called "push to deploy":<br class="m_-966806696353180239gmail_msg">
<br class="m_-966806696353180239gmail_msg">
<a href="https://github.com/blog/1957-git-2-3-has-been-released" rel="noreferrer" class="m_-966806696353180239gmail_msg" target="_blank">https://github.com/blog/1957-<wbr>git-2-3-has-been-released</a><br class="m_-966806696353180239gmail_msg">
<br class="m_-966806696353180239gmail_msg">
To use this, you have to set config "receive.denyCurrentBranch =<br class="m_-966806696353180239gmail_msg">
updateInstead" on the server copy of the repository.<br class="m_-966806696353180239gmail_msg">
<br class="m_-966806696353180239gmail_msg">
Otherwise: normally what happens is pushing to the repo updates the<br class="m_-966806696353180239gmail_msg">
objects in the repo but *not* the checked-out working copy, which can<br class="m_-966806696353180239gmail_msg">
get your repo into a very confusing state.  See:<br class="m_-966806696353180239gmail_msg">
<br class="m_-966806696353180239gmail_msg">
<a href="https://git.wiki.kernel.org/index.php?title=Git_FAQ&oldid=23811#Why_won.27t_I_see_changes_in_the_remote_repo_after_.22git_push.22.3F" rel="noreferrer" class="m_-966806696353180239gmail_msg" target="_blank">https://git.wiki.kernel.org/<wbr>index.php?title=Git_FAQ&oldid=<wbr>23811#Why_won.27t_I_see_<wbr>changes_in_the_remote_repo_<wbr>after_.22git_push.22.3F</a><br class="m_-966806696353180239gmail_msg">
<br class="m_-966806696353180239gmail_msg">
</blockquote></div>
</div></div><br>______________________________<wbr>_________________<br>
Password-Store mailing list<br>
<a href="mailto:Password-Store@lists.zx2c4.com">Password-Store@lists.zx2c4.com</a><br>
<a href="https://lists.zx2c4.com/mailman/listinfo/password-store" rel="noreferrer" target="_blank">https://lists.zx2c4.com/<wbr>mailman/listinfo/password-<wbr>store</a><br>
<br></blockquote></div><br></div>