Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would have one person who is in charge of deploying to the different servers, especially staging and production. That way when you create a release branch, this branch would be deployed on the staging server. When the release branch is finished you deploy the master branch to the production server.</p> <p>You can clone the repo to staging and production, just make sure the .git directory has proper security <em>(.htaccess is your friend :))</em>, so that non-developers can't access that directory.</p> <p>I would use git pull on the production server. I've read about rsync and hooks as well, but just git works just fine for me.</p> <p>Now sometimes when I work for a client that doesn't don't allow git on the server and I use ftp. There is a Pyhton program on github called <a href="https://github.com/ezyang/git-ftp" rel="nofollow">git-ftp</a> which I adapted a little bit to accommodate git-flow. I haven't put that version on github, maybe I should.</p> <p><strong><em>As a follow up to the first comment</em></strong><br> The person who does the staging and production releases would do the following steps on his/her local machine:</p> <pre><code>git flow release start -F 1.0 </code></pre> <p>do some work, like update version number Publish it to github</p> <pre><code>git flow release publish 1.0 </code></pre> <p>On the staging server:</p> <pre><code>git pull origin release/1.0 </code></pre> <p>After the staging period is over, on the local machine</p> <pre><code>git flow release finish 1.0 </code></pre> <p>On the production server</p> <pre><code>git pull origin master </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POGit flow with Github deployment
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPeter van der Does
    1. USPeter van der Does
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGit flow with Github deployment
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks Peter. So just use GIT the same way on staging and production as I would on my local or development server but pull from master instead of develop? i.e git pull origin master
      singulars
      1. PO
      1. USDerek Carlisle
    2. COYeah, that's how I would do it, I updated the answer to show the steps. I might have missed a few small steps, but that would be the way to go, IMHO
      singulars
      1. PO
      1. USPeter van der Does
    3. COThanks. When you say update version number does git flow do this as part of `git flow release publish 1.0`? Whats the difference between publishing the release whilst its still open locally and finishing the release locally and pushing to github?
      singulars
      1. PO
      1. USDerek Carlisle
 

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