<p>I wouldn't do it, personally.  Especially if your plugin interacts with the database and you'll be creating/deleting tables, altering the schema, needing to restore the database, etc.</p>

<p>Too much risk in breaking the live site and very little benefit.</p>

CC BY-SA 3.0
2015-02-28T04:48:01.260Z
2015-02-28T04:48:01.260Z
Brad Bell
<p>I've setup a dev site on a subdomain alongside the production site and modified the config.php and db.php files on both installs for a multi-environment config. Since I only need to work on plugins and template files on the 'dev' site, would it be crazy to have the 'dev' site use the same mysql database as the live site? What would be the downfall in doing this?</p>

<database><multi-environment>
Multi-Env Craft Setup sharing DB
# Multi-Env Craft Setup sharing DB

(Asked by: username_0 on 2015-02-28)

I've setup a dev site on a subdomain alongside the production site and modified the config.php and db.php files on both installs for a multi-environment config. Since I only need to work on plugins and template files on the 'dev' site, would it be crazy to have the 'dev' site use the same mysql database as the live site? What would be the downfall in doing this?

**Tags:** database, multi-environment


---

## 1 answers

### Answer by username_1 on 2015-02-28. Score: 4 | Accepted answer

I wouldn't do it, personally. Especially if your plugin interacts with the database and you'll be creating/deleting tables, altering the schema, needing to restore the database, etc.

Too much risk in breaking the live site and very little benefit.


---

