Git push still throwing RPC error after changing postBuffer

So, since I use Webfaction, I followed their git tutorial and ran this on my git instance:

$ git config http.postBuffer 524288000 

To be clear, here's what in the config my repo:

 $ cat config [core] repositoryformatversion = 0 filemode = true bare = true [http] receivepack = true postBuffer = 524288000 

Despite this, this is still happening:

 $ git push Counting objects: 74, done. Delta compression using up to 4 threads. Compressing objects: 100% (62/62), done. error: RPC failed; result=22, HTTP code = 411 fatal: The remote end hung up unexpectedly Writing objects: 100% (73/73), 3.67 MiB | 962 KiB/s, done. Total 73 (delta 3), reused 0 (delta 0) fatal: The remote end hung up unexpectedly 

The crazy thing is that I don’t even push so much data: only about 120 MB. Now I'm still new to git, so I thought I could publish the local .git/config file as well:

 $ cat .git/config [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = http://USERNAME: PASSWORD@MY.DOMAIN.TLD /REPONAME.git [branch "master"] remote = origin merge = refs/heads/master 

Honestly, I have absolutely no ideas. If someone can understand what I did wrong, I would really appreciate it. Note that I know I can do this via SSH, but this is not ideal for my scenario.

+4
source share
1 answer

So, after some blind setup (and some sleep), I realized that the problem was actually where I ran the postBuffer command. I ran it at the end of the repo, not client side. As soon as I ran it on the client side, everything worked fine.

Sorry to confuse everyone.

+6
source

Source: https://habr.com/ru/post/1395860/


All Articles