StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POGit Development to Production Setup
primarykey
Id
12486207
data
AcceptedAnswerId
12489556
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-09-18T22:51:20.877
FavoriteCount
1
LastActivityDate
2012-09-19T15:44:32.270
LastEditDate
LastEditorUserId
0
OwnerUserId
756487
ParentId
0
PostTypeId
1
Score
3
ViewCount
2046
LastEditorDisplayName
text
Body
I know questions like this have been asked a lot. But, I'm not finding an exact answer to my problem. I'm in the process of starting to use Git. I have no prior experience with Git or any type of version control for that matter. So far I've been able to get it up and running locally with no problem. I'm able use Git through the terminal and I've also started tinkering around with the SourceTree app. My problems arise when I try to set things up remotely. I have Git installed on the server. I've created a repository on my remote staging server. I can push up to it via SourceTree. However, it doesn't seem like the remote repository is connected to the web root. I make a change on a branch locally, commit, merge and then push up to the remote. But, those changes are not on the served pages via the staging server? On the remote I created a directory outside of my web root to hold the repository projects. I created a subdirectory inside of it called mygit.git. This is where I created my remote repository using the git init --bare. This should create a repo without a working directly that I can push to. This is the environment I'm working with <pre><code>Production (remote server) ^ Staging (remote server) ^ Development (local) </code></pre> So, my questions are: <ol> <li>Why is the web server not displaying changes made via the local push</li> <li>Should I have repository on my Production server as well that all the changes sort of bubble up to?</li> <li>Am I doing this all wrong?</li> </ol> Thanks for any help on this.
Tags
<git><repository>
Title
Git Development to Production Setup
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMAZUMA
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
3. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POGit Development to Production Setup
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POGit Development to Production Setup
 UserUserId
 USVonC
 VoteTypeVoteTypeId
 VTFavorite
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.