StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6556829
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-07-02T11:54:02.947
FavoriteCount
0
LastActivityDate
2011-07-03T09:45:30.660
LastEditDate
2011-07-03T09:45:30.660
LastEditorUserId
583715
OwnerUserId
583715
ParentId
233421
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
On Windows, you can also serve Git repositories with Apache over HTTP or HTTPS, using the DAV extension. The Git repository path can then be protected with Apache authentication checks such as restricting to certain IP addresses or htpasswd/htdigest type authentication. The limitation of using htpasswd/htdigest authentication is that the username:password is passed in the requested Git URL, so restricting access to the Git URL to certain IP addresses is better. Edit: Note, you can leave the password out of the Git URL and Git will prompt you for the password on push and fetch/pull instead. Using HTTPS means all the data is encrypted in transfer. It's easy enough to set up, and works. The following example shows the combination of access control by IP address and user:password over standard HTTP. Example Apache Virtualhost <pre><code>## GIT HTTP DAV ## <VirtualHost *:80> ServerName git.example.com DocumentRoot C:\webroot\htdocs\restricted\git ErrorLog C:\webroot\apache\logs\error-git-webdav.log <Location /> DAV on # Restrict Access AuthType Basic AuthName "Restricted Area" AuthUserFile "C:\webroot\apache\conf\git-htpasswd" # To valid user Require valid-user # AND valid IP address Order Deny,Allow Deny from all # Example IP 1 Allow from 203.22.56.67 # Example IP 2 Allow from 202.12.33.44 # Require both authentication checks to be satisfied Satisfy all </Location> </VirtualHost> </code></pre> Example .git/config <pre><code>[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = http://username:password@git.example.com/codebase.git [branch "master"] remote = origin merge = refs/heads/master </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHosting Git Repository in Windows
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDavid Thomas
UserOwnerUserId
1. USDavid Thomas
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
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.