Development workflow, functional testing, etc.

Tuesday 25 March 2008 4:55:10 am

I'd love to hear how other developers work with ez publish. I have several clients on this platform now, and we are constantly adding and removing features, changing templates, modules, etc. For code this is not really a problem, as I keep that in subversion. What is more of a problem is when I need to add or make changes to content classes, add or remove permissions, etc. Everything is so tightly coupled to the production database. On other projects I have worked on, we some times pulled the production data into development, then pushed everything back out again at deployment. However, as soon as you start to use forums, order forms, etc, this is no longer a viable option, as production data is changing constantly. How do you deal with this? Could we maybe get a thread running with some "best practices"?

-Erlend

Saturday 11 October 2008 3:27:20 am

Here's some links, and it's definitely worth continuing this thread. eZ Systems may have a clever way to do this, but I've not heard anything that has resolved maintaining database configuration across multiple environments.

http://www.cjohansen.no/ez_publish/praktisk_ez_publish
http://suffandnonsense.blogspot.com/2008/10/how-to-you-handle-revision-control-in.html