Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I also followed the same guide at toroid.org, but I'd like to note that although you started with a bare repository, by adding a working directory, extra handling will most likely be needed. I found that the following hook is useful if you have content that may change dynamically or otherwise and don't want to lose data when using <code>git checkout -f</code></p> <p>pre-receive</p> <pre><code>#!/bin/sh git add -A git diff --quiet --cached if [ $? -gt 0 ]; then git commit --quiet -m "autocommit" echo "Working Directory was out of sync. Pull to receive updated index." exit 1 fi </code></pre> <p>This will stop a push if there are changes in the remote working directory. Think of it as someone (the web server) making changes but forgetting to commit them. Using <code>checkout</code> with the <code>-f</code> will discard those changes. This hook is a good place to prevent this from happening, but it would be nice if there was also a hook called on the remote server prior to a pull so that you would receive these changes seamlessly.</p> <p>post-receive</p> <pre><code>#!/bin/sh git checkout -f echo "Working directory synced." </code></pre> <p>Regarding have two branches, I thought your first solution was more elegant than having to deal with multiple repositories. If you really want to keep your production site isolated, you could use rsync locally which has similar delta patching. I would have a testing and stable branch in the repository with only the testing site as the working directory. When ready to release merge the testing into the stable branch, push, and have a hook looking for commits to stable branch make the call to rsync.</p>
    singulars
    1. This table or related slice is empty.
    1. POGit for Websites / post-receive / Separation of Test and Production Sites
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UStcp
    1. UStcp
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 for the pre-receive comment - that's a really useful tip, thanks. As far as multiple repos, it's not too bad in actuality :) rsync is definitely another viable option though. Thanks!
      singulars
      1. PO
      1. USWalt W
    2. CO`git add .` wasn't picking up all the changes (deletions), changed to `git add -A`
      singulars
      1. PO
      1. UStcp
 

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