Databases
StackOverflow2013
Postsdbo
PONext Steps with Git: Establishing a Cohesive Work Flow
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONext Steps with Git: Establishing a Cohesive Work Flow
    primarykey
    data
    text
    <p>I am new to git and distributed version control but have managed, without much stumbling, to <code>init</code> my own local source, setup a private remote repository (origin) via ssh on my own web host, and do the basic <code>pull</code> and <code>push</code> from master to origin. (I even testing a clone!)</p> <p>I think I have the single-direction, git work flow under control. Now, however, I'm starting to think about how I handle moving things between development, beta, and production. Most tutorials I've found talk about different users merging and cloning and pulling and pushing, but in my case, it's just me, handling things from different sources.</p> <p>Am hoping an experienced git user could provide some insight into my work flow and provide some suggestions on how they would handle merging, branches, etc (things I am not too familiar/comfortable with, yet).</p> <p>Here are the different machines/locations I will have:</p> <ol> <li>Remote main git store: ssh://git@example.com/git/myproject.git</li> <li>Home web server, main development box (where I sit, privately, and do most of the work)</li> <li>Remote web server, beta testing (public facing): <a href="http://beta.example.com" rel="nofollow noreferrer">http://beta.example.com</a> (test my dev work before production)</li> <li>Remote web server, production site: <a href="http://example.com" rel="nofollow noreferrer">http://example.com</a> (where real people, hopefully, use the site)</li> <li>(Occasionally) traveling around on a laptop (running its own local web server).</li> </ol> <p>How would you handle this? Thanks in advance.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USthornomad
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PONext Steps with Git: Establishing a Cohesive Work Flow
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PONext Steps with Git: Establishing a Cohesive Work Flow
      1. USknorv
      1. VTFavorite
    3. VO
      singulars
      1. PONext Steps with Git: Establishing a Cohesive Work Flow
      1. This table or related slice is empty.
      1. VTUpMod
    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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload