Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>To add another possibility, you can <a href="https://stackoverflow.com/a/14750116/6309">define a proxy through the <code>git config http.proxy</code></a>.</p> <pre><code>git config --global http.proxy http://mydomain\\myusername:mypassword@myproxyserver:proxyport </code></pre> <p>But what is really neat is, <a href="https://github.com/git/git/blob/bb80ee09974667a1db6bbc5e33574ed869b76a88/Documentation/RelNotes/1.8.5.txt#L69-L78" rel="noreferrer">starting git1.8.5 (October 2013)</a>, you can <strong>set http settings per url</strong>.</p> <p><strong>The "<code>http.*</code>" variables can now be specified per URL that the configuration applies</strong>.<br> For example,</p> <pre><code>[http] sslVerify = true [http "https://weak.example.com/"] sslVerify = false </code></pre> <blockquote> <p>would flip <code>http.sslVerify</code> off only when talking to that specified site.</p> </blockquote> <hr> <p>See <a href="https://github.com/git/git/commit/d4770964d5058a679ebfc051acceb7968a831f84" rel="noreferrer">commit d4770964d5</a>:</p> <pre><code>$ git config --bool --get-urlmatch http.sslVerify https://good.example.com true $ git config --bool --get-urlmatch http.sslVerify https://weak.example.com false </code></pre> <blockquote> <p>With only <code>&lt;section&gt;</code> specified, you can get a list of all variables in the section with their values that apply to the given URL. E.g</p> </blockquote> <pre><code>$ git config --get-urlmatch http https://weak.example.com http.sslverify false </code></pre> <hr> <p>All the details are in <a href="https://github.com/git/git/commit/6a56993b2ec7082521cf14f98ab9fb5a5def4b13" rel="noreferrer">commit 6a56993b</a>:</p> <pre><code>http.&lt;url&gt;.*:: </code></pre> <blockquote> <p>Any of the http.* options above can be applied selectively to some urls.<br> For a config key to match a URL, each element of the config key is compared to that of the URL, in the following order:</p> </blockquote> <ul> <li><strong>Scheme</strong> (e.g., <code>https</code> in <code>https://example.com/</code>).</li> <li><strong>Host/domain name</strong> (e.g., <code>example.com</code> in <code>https://example.com/</code>).</li> <li><strong>Port number</strong> (e.g., <code>8080</code> in <code>http://example.com:8080/</code>).</li> <li><strong>Path</strong> (e.g., <code>repo.git</code> in <code>https://example.com/repo.git</code>). </li> <li><strong>User name</strong> (e.g., <code>user</code> in <code>https://user@example.com/repo.git</code>)</li> </ul> <blockquote> <p>The list above is ordered by decreasing precedence; a URL that matches a config key's path is preferred to one that matches its user name.<br> For example, if the URL is <code>https://user@example.com/foo/bar</code> a config key match of <code>https://example.com/foo</code> will be preferred over a config key match of <code>https://user@example.com</code>.</p> <p>All URLs are normalized before attempting any matching (the password part, if embedded in the URL, is always ignored for matching purposes) so that equivalent urls that are simply spelled differently will match properly. </p> <p><strong>Environment variable settings always override any matches</strong>.<br> The urls that are matched against are those given directly to Git commands.<br> This means any URLs +visited as a result of a redirection do not participate in matching. </p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POOnly use a proxy for certain git urls/domains?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USVonC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload