Git

Search results for http

  1. Smart HTTP

    /book/en/Git-on-the-Server-Smart-HTTP

    Smart HTTP We now have authenticated access through SSH and unauthenticated access through git://, but there is also a protocol

  2. git-http-fetch

    /docs/git-http-fetch

    git-http-fetch(1) ================= NAME ---- git-http-fetch - Download from a remote Git repository via HTTP SYNOPSIS -------- [verse] 'git http-fetch' [-c] [-t] [-a] [-d] [-v] [-w

  3. http-protocol

    /docs/http-protocol

    HTTP transfer protocols ======================= Git supports two HTTP based transfer protocols. A "dumb" protocol which requires only a standard HTTP server on the server end of the connection, and

  4. git-http-backend

    /docs/git-http-backend

    git-http-backend(1) =================== NAME ---- git-http-backend - Server side implementation of Git over HTTP SYNOPSIS -------- [verse] 'git http-backend' DESCRIPTION ----------- A simple CGI

  5. gitprotocol-http

    /docs/gitprotocol-http

    gitprotocol-http(5) =================== NAME ---- gitprotocol-http - Git HTTP-based protocols SYNOPSIS -------- [verse] DESCRIPTION ----------- Git supports two HTTP

  6. git-http-push

    /docs/git-http-push

    git-http-push(1) ================ NAME ---- git-http-push - Push objects over HTTP/DAV to another repository SYNOPSIS -------- [verse] 'git http-push' [--all] [--dry-run] [--force] [--verbose

  1. The Protocols

    /book/en/Git-on-the-Server-The-Protocols

    class="paragraph"> Git can use four distinct protocols to transfer data: Local, HTTP, Secure Shell (SSH) and Git. Here we’ll discuss what they are and in what basic circumstances you would want (or not

  2. Transfer Protocols

    /book/en/Git-Internals-Transfer-Protocols

    repository to be served read-only over HTTP, the dumb protocol is likely what will be used. This protocol is called “dumb” because it requires no Git-specific code on the server side during the transport

  3. GitLab

    /book/en/Git-on-the-Server-GitLab

    projects that belong to that user. If the user jane had a project named project, that project’s URL would be http://server/jane/project

  4. go-git

    /book/en/Appendix-B:-Embedding-Git-in-your-Applications-go-git

    fine-tunable HTTP client, such as the one found at https://github.com/go

  5. GitWeb

    /book/en/Git-on-the-Server-GitWeb

    server; if you prefer to use something else, it shouldn’t be difficult to set up. At this point, you should be able to visit http://gitserver/

  6. Scripting GitHub

    /book/en/GitHub-Scripting-GitHub

    repository hooks are pretty simple. You specify a URL and GitHub will post an HTTP payload to that URL on any event you want. Generally the way this works is you

  7. Environment Variables

    /book/en/Git-Internals-Environment-Variables

    over HTTP, so GIT_CURL_VERBOSE tells Git to emit all the messages generated by that library. This is similar to doing curl -v on the command line.

  8. Setup and Config

    /book/en/Appendix-C:-Git-Commands-Setup-and-Config

    default when you run git pull. In Credential Storage we used it to set up a default store for your HTTP

  9. Signing Your Work

    /book/en/Git-Tools-Signing-Your-Work

    883653babd8ee7ea23e6a5c392bb739348b1eb61 type commit tag v1.4.2.1 tagger Junio C Hamano <junkio@cox.net> 1158138501 -0700 GIT 1.4.2.1 Minor fixes since 1.4.2, including git-mv and git-http with alternates. gpg

  10. git-upload-pack

    /docs/git-upload-pack

    . --stateless-rpc:: Perform only a single read-write cycle with stdin and stdout. This fits with the HTTP POST request processing model where a program may read the request, write a response, and must exit

  11. git-credential-cache

    /docs/git-credential-cache

    username or password. For example: ------------------------------------ $ git config credential.helper cache $ git push http://example.com/repo.git Username: Password:

  12. gitweb

    /docs/gitweb

    parameter (i.e. "$projectroot/$project"). + For example, if you use mod_perl to run the script, and have dumb HTTP protocol authentication configured for your repositories, you can use the following hook to

  13. gitfaq

    /docs/gitfaq

    every commit you make. + This configuration doesn't have any effect on authenticating to remote services; for that, see `credential.username` in linkgit:git-config[1]. [[http-postbuffer]] What does

  14. git-credential-store

    /docs/git-credential-store

    this helper is to reduce the number of times you must type your username or password. For example: ------------------------------------------ $ git config credential.helper store $ git push http

scroll-to-top