StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14670278
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-02-03T07:11:21.890
FavoriteCount
0
LastActivityDate
2013-02-03T22:56:34.950
LastEditDate
2013-02-03T22:56:34.950
LastEditorUserId
577081
OwnerUserId
577081
ParentId
14667128
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<p>You have to create a bare repository on the server with <code>git init --bare</code>. Then use a <code>post-receive</code> hook to trigger your deploy. How you deploy is up to you.</p> <h2>My Deployment Strategy</h2> <p>I usually place a <code>deploy</code> director, somewhere logical. Then each checkout, I unpack the latest branch to <code>deploy/COMMIT_ID</code> where <code>COMMIT_ID</code> is the hash of the latest push. Once the checkout is complete, you can re-point a symlink to the latest deployment directory.</p> <p>My usual directory structure:</p> <pre><code>deploy.git/ deploy/ a7922231/ b2f0a2af/ latest -> b2f0a2af </code></pre> <h3>Unpacking the Update</h3> <p>Rather than use a <code>git-checkout</code>, I usually use <code>git-archive</code> to unpack a branch into a directory.</p> <pre><code># Assuming current directory is deploy.git HEAD=`cat refs/heads/master` mkdir -p ../deploy/${HEAD} git archive master | tar -x -C ../deploy/${HEAD} </code></pre> <p>Your web-server can point to <code>deploy/latest</code>, updates will be more-or-less atomic.</p> <p>I use this often in production, and has a few benefits over unpacking over the same directory.</p> <ol> <li>rollbacks are easy</li> <li>you can do post-unpack procedures, like compile or install dependencies without interrupting the current deployment</li> </ol> <h3>Tips</h3> <ol> <li>each update, append to a <strong>deploy log</strong> that says when updates occurred, and what their hash ids are. This makes rollbacks <em>much</em> easier.</li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow can I automagically make a checkout upon push?
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJacob Groundwater
UserOwnerUserId
1. USJacob Groundwater
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow can I automagically make a checkout upon push?
  singulars
  PostTypePostTypeId
  PTQuestion
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
  VTAcceptedByOriginator
3. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. COHow do you checkout into an arbitrary directory? What is the option I need to pass to git checkout?
  singulars
  PostPostId
  PO
  UserUserId
  USfuz

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.