Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>What you say makes sense : it's pretty close to what I often use <em>(sometimes with ant, sometimes with phing, and sometimes with some shell-scripts)</em>.</p> <p>In the <code>build</code> directory, I would have something like this :</p> <pre><code>build/ testing/ development/ staging/ production/ common/ </code></pre> <p>With one <code>build.xml</code> file in each sub-directory -- all including another <code>build.xml</code> file, located in the <code>common</code> directory, the idea being to put as much "common" code as possible in the "common" <code>build.xml</code> file, and to have per-environment specific files, that contain as few xml code as possible.</p> <p>This can be done with the <a href="http://phing.info/docs/guide/trunk/chapters/appendixes/AppendixB-CoreTasks.html#ImportTask" rel="nofollow noreferrer"><code>import</code></a> task that exists in the last version of phing <em>(not sure it's in the stable version -- I'm using an SVN checkout of phing, to have this one, for the project I'm currently working on)</em>.</p> <p><br> One thing, though : you say you want to deploy to production from the production server ; I would rather, instead :</p> <ul> <li>on a "development" server : <ul> <li>export from SVN </li> <li>compress JS/CSS and all that</li> <li>create a tar.gz archive</li> </ul></li> <li>upload that archive to the production server</li> <li>on the "production" server : <ul> <li>un-compress that uploaded archive</li> <li>change a couple of symlink to use the new version of the sources (see the answer I gave <a href="https://stackoverflow.com/questions/1395992/updating-a-web-app-without-any-downtime/1396015#1396015">here</a>, for more informations)</li> <li>update what has to be done in the DB</li> </ul></li> </ul> <p>The idea being to :</p> <ul> <li>do as few things as possible on the production server <ul> <li>just in case something goes wrong</li> <li>and in case, one day, your production server doesn't have access to the SVN server</li> </ul></li> <li>to have a physical archive that can be deployed on several production servers</li> </ul> <p><br> Oh, and, as a sidenote : you have to write some kind of documentation of "how to deploy to production", step by step !</p> <p>This will be really useful the day you are in holiday and someone else has to deploy to production because of an urgent bug-fix ;-)</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do you manage your build [using Phing] process?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USPascal MARTIN
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do you manage your build [using Phing] process?
      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. VTUpMod
    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. VTAcceptedByOriginator
    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