title: How to direct git-lfs traffic for multiple remotes to a single endpoint?
body: <p>I use a workstation to develop and two remotes to store: a local (LAN) git server [origin] and a hosted (e.g. bitbucket/github) git server [cloud] for extra backup. </p>
  
  <p>I am currently using git lfs to track png files and my available online storage is running out. As a solution, I'd like to store png files exclusively on the origin remote. To achieve this I have attempted to configure the lfsurl for my cloud endpoint to be the same as the origin. This way, I expect that pushing a png to either git endpoint would result in the image going to the same location (and <em>ignored</em> in the cloud push?).</p>
  
  <p>For a given repo here are samples of my git config files:</p>
  
  <p><strong>.git/config</strong></p>
  
  <blockquote>
    <p>[remote "origin"] <br/>
    url = ssh://git@git.myserver.com:7999/project/repo-data.git<br/>
    [remote "cloud"] <br/>
    url = git@bitbucket.org:user/repo-data.git<br/></p>
  </blockquote>
  
  <p><strong>.lfsconfig</strong></p>
  
  <blockquote>
    <p>[remote "cloud"]<br/>
    lfsurl = <a href="https://git.myserver.com/project/repo-data.git/info/lfs" rel="noreferrer">https://git.myserver.com/project/repo-data.git/info/lfs</a></p>
  </blockquote>
  
  <p>Output from git lfs env</p>
  
  <pre><code>$ git lfs env
  Endpoint=https://git.myserver.com/project/repo-data.git/info/lfs (auth=none)
  Endpoint (cloud)=https://git.myserver.com/project/repo-data.git/info/lfs (auth=none)
  </code></pre>
  
  <p>The above configuration is functional as images are pushed to git lfs. Unfortunately the images continue to be pushed to <em>both</em> remotes (origin + cloud). I expect the pointer file on the cloud remote, but no png. </p>
  
  <p>I suspect my lfsurl is incorrect and git lfs is falling back to the default url for each remote, but I see no errors or warnings. Are there tools/logs to troubleshoot?</p>
  
  <p>How to direct git lfs traffic for multiple remotes to a single endpoint?</p>
  
  <p>Thanks.</p>