<p>I'd recommend you take a look at the excellent existing threads on this:</p>

<ul>
<li><a href="https://craftcms.stackexchange.com/a/62/480">Git Workflow and Multi Environment - how to approach</a></li>
<li><a href="https://craftcms.stackexchange.com/questions/10/whats-the-best-practice-for-handling-data-migration-and-organization-across-dev">What's the best practice for handling data migration and organization across development environments?</a></li>
</ul>

<p>as well as the official documentation on <a href="http://buildwithcraft.com/docs/multi-environment-configs" rel="nofollow noreferrer">Multi-Environment Configs</a></p>

CC BY-SA 3.0
2015-01-10T09:50:42.580Z
2015-01-10T09:50:42.580Z
2017-04-13T12:51:00.200Z
Fred Carlsen
<p>I'm setting up a new site using Craft and would like to know what's the best way to manage dev and production environments? For instance, keeping entries/fields/ and control panels configurations sane across both environments? </p>

<multi-environment>
Correct way to set up development and production environments for Craft?
# Correct way to set up development and production environments for Craft?

(Asked by: username_0 on 2015-01-10)

I'm setting up a new site using Craft and would like to know what's the best way to manage dev and production environments? For instance, keeping entries/fields/ and control panels configurations sane across both environments?

**Tags:** multi-environment


---

## 1 answers

### Answer by username_1 on 2015-01-10. Score: 6 | Accepted answer

I'd recommend you take a look at the excellent existing threads on this:

* [Git Workflow and Multi Environment - how to approach](https://craftcms.stackexchange.com/a/62/480)
* [What's the best practice for handling data migration and organization across development environments?](https://craftcms.stackexchange.com/questions/10/whats-the-best-practice-for-handling-data-migration-and-organization-across-dev)

as well as the official documentation on [Multi-Environment Configs](http://buildwithcraft.com/docs/multi-environment-configs)


---

