Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is a very common situation - and there are a couple of things you probably want to consider. </p> <p>Firstly, as Klas Melbourn writes, you probably don't want to add content or data from the live system to your source code control - that's what back-ups are for.</p> <p>The second thing to consider is to introduce the concept of "environment" to your thinking - in most cases, you have at least 3 environments: Development - your machine, your friend's machine. The development environment should be predictable - so you probably want to have a bunch of representative user contributions in there, so you can test your code - but it should not (usually) have a complete copy of the live site content/data, because that slows your development process without adding much value. On Dev environments, you want to have lots of debugging information, including "rich" error messages. </p> <p>The next environment is usually Test - you and your friend put your work together, and test it on a dedicated environment. Again, you want the content and data to be representative, but probably not include all the data from live. You do, however, want to have examples of edge cases - massive image, tiny image, image in weird aspect ratios etc. - so you can quickly test that everything works as you expect. </p> <p>The final environment is "production" or "live" - here you obviously don't want the test data floating around, and you want to disable "rich" error messages, debug information, test accounts etc. </p> <p>Managing all this can be a bit of a pain, and the most recent thinking is "<a href="http://en.wikipedia.org/wiki/Continuous_delivery" rel="nofollow noreferrer">Continuous Delivery</a>"; check out <a href="https://stackoverflow.com/questions/2180460/setting-up-a-deployment-build-ci-cycle-for-php-projects">this answer</a> for a way to do this with PHP. </p>
    singulars
    1. This table or related slice is empty.
    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. This table or related slice is empty.
 

Querying!

 
Guidance

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