Databases
StackOverflow2013
Postsdbo
POPrevent file differences between live and staging websites AND system scripts (PHP)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPrevent file differences between live and staging websites AND system scripts (PHP)
    primarykey
    data
    text
    <p>I'm trying to find a good way to maintain PHP configuration differences between a dev and live environment. I know how to handle differences when scripts are run by Apache (<em>see below</em>), but not when they are run <strong>on the command line</strong>, e.g. via cron.</p> <p><em>Background info:</em></p> <p><strong><em>What do I mean by "configuration differences"?</em></strong> Like most code shops, we run a non-public 'staging' version of our website where we test code before it goes to the live website. We use Subversion and have the live website as 'Trunk' and 'Staging' as a branch. It makes life easier when code goes from staging to live if the repository version of the files have minimal differences. But obviously, some details need to be different, e.g. the DB connection details.</p> <p><strong><em>How configuration differences are solved with Apache</em></strong></p> <p>In PHP, we set branch specific variables as follows:</p> <pre><code>switch ($_SERVER['HTTP_HOST']) { case 'ourstagingurl.com': $dbPassword = "blahblah"; break; default: $dbPassword = "blahblah"; } </code></pre> <p>or we put the following in the .htaccess file relevant to the specific site:</p> <pre><code>php_value dbPassword "blahblah" </code></pre> <p><strong><em>Why I can't resolve configuration differences using the CLI?</em></strong></p> <p>When a script is run on the CLI, there's no super globals such as <code>$_SERVER</code>. I could <code>include</code> a config file using a absolute path but how can I know whether the script is from live or staging? I could pass in a command line argument that specifies the environment but I was hoping there was a better way?</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. USTom
    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. POPrevent file differences between live and staging websites AND system scripts (PHP)
      1. USDeebster
      1. VTFavorite
    2. VO
      singulars
      1. POPrevent file differences between live and staging websites AND system scripts (PHP)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPrevent file differences between live and staging websites AND system scripts (PHP)
      1. USprogrammernovice
      1. VTFavorite
    1. COJust a suggestion coming from nowhere: how about letting each live-version reside in a tag? That way you can always simulate a previous live-version and use the trunk as stage. Just ignore this OT-comment if you feel like it :)
      singulars
      1. POPrevent file differences between live and staging websites AND system scripts (PHP)
      1. USchelmertz
 

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