Search results for http
-
Smart HTTP
/book/en/Git-on-the-Server-Smart-HTTPSmart HTTP We now have authenticated access through SSH and unauthenticated access through git://, but there is also a protocol
-
git-http-fetch
/docs/git-http-fetchgit-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
-
http-protocol
/docs/http-protocolHTTP 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
-
git-http-backend
/docs/git-http-backendgit-http-backend(1) =================== NAME ---- git-http-backend - Server side implementation of Git over HTTP SYNOPSIS -------- [verse] 'git http-backend' DESCRIPTION ----------- A simple CGI
-
gitprotocol-http
/docs/gitprotocol-httpgitprotocol-http(5) =================== NAME ---- gitprotocol-http - Git HTTP-based protocols SYNOPSIS -------- [verse] DESCRIPTION ----------- Git supports two HTTP
-
git-http-push
/docs/git-http-pushgit-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
-
The Protocols
/book/en/Git-on-the-Server-The-Protocolsclass="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
-
Transfer Protocols
/book/en/Git-Internals-Transfer-Protocolsrepository 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
-
GitLab
/book/en/Git-on-the-Server-GitLabprojects that belong to that user. If the user jane had a project named project, that project’s URL would be http://server/jane/project
-
go-git
/book/en/Appendix-B:-Embedding-Git-in-your-Applications-go-gitfine-tunable HTTP client, such as the one found at https://github.com/go
-
GitWeb
/book/en/Git-on-the-Server-GitWebserver; 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/
-
Scripting GitHub
/book/en/GitHub-Scripting-GitHubrepository 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
-
Environment Variables
/book/en/Git-Internals-Environment-Variablesover 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.
-
Setup and Config
/book/en/Appendix-C:-Git-Commands-Setup-and-Configdefault when you run git pull. In Credential Storage we used it to set up a default store for your HTTP
-
Signing Your Work
/book/en/Git-Tools-Signing-Your-Work883653babd8ee7ea23e6a5c392bb739348b1eb61 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
-
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
-
git-credential-cache
/docs/git-credential-cacheusername or password. For example: ------------------------------------ $ git config credential.helper cache $ git push http://example.com/repo.git Username: Password:
-
gitweb
/docs/gitwebparameter (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
-
gitfaq
/docs/gitfaqevery 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
-
git-credential-store
/docs/git-credential-storethis 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