set up a testing environment – but NOT locally? and using the same DB *tables*?

Viewing 3 replies - 1 through 3 (of 3 total)

  • I realize you probably found your answer months ago. That being said, I think the answer to your question is that when installing WP in dev.mysite.com, rather than make a new WP installation, you should simply copy the WP from your mysite.com installation.

    That way, the wp-config.php file will point to your existing database and tables, and WP should not create new tables.

    Note: because your blog and WP URLs will be new for the dev.mysite.com site, you should run wp-admin.php in the dev site and update those URL’s wthin the General Settings form.

    I realize you probably found your answer months ago. That being said, I think the answer to your question is that when installing WP in dev.mysite.com, rather than make a new WP installation, you should simply copy the WP from your mysite.com installation.

    That way, the wp-config.php file will point to your existing database and tables, and WP should not create new tables.

    Note: because your blog and WP URLs will be new for the dev.mysite.com site, you should run wp-admin.php in the dev site and update those URL’s wthin the General Settings form.

    I feel compelled to point out that – should you get such a setup to work somehow – using the same tables for dev and live is very risky, as changes to dev could easily break your production site.

    Better by far to keep the two seperate, it’s not like you need all your live content in dev.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘set up a testing environment – but NOT locally? and using the same DB *tables*?’ is closed to new replies.