Managing Environments and DataCreated 3 years ago by failcookie
This week I have been looking at how I can use Pyro for ongoing client retainers and I wanted to gather some thoughts on some of the best ways to manage data shared between dev environments.
Our standard environments are usually broken down into:
- Dev environment shared between up to 4 devs
- Staging environment for showing client and gathering initial feedback
Most of the module work and smaller custom stuff won't be much of an issue. The bigger issues I see fall more towards content and ongoing content creation. If we create a page template, we would have to go through and replicate everything across our dev setups, our staging environment and our production. Some pages aren't that rough to replicate, but some pages do have a lot of content and field types to support it. Especially once we bring in grids and have to replicate each grid.
Has anyone found an efficient solution for handling data like this? One of my thoughts was making use of migrations for at least handling field type data, but I haven't tested this theory out yet.