handling sites with lots of editors and devs

[Neeks]

I want to get some tips from the community about using process-wire in production environments. 

Workflows for lots of devs and editors, any tips?

I am wondering if any one has used processwire in an APP or site that has lots of editors, and many devs all needing access a site to be able to make changes to nodules, content, codebase, etc. If so, how do you handle it, what is your workflow and how do you keep things sane?

Adapting to existing workflow: any tips?

I am currently working at a company where we have lots of test server environments, and most of our changes are through git. So in our workflow we are pushing changes from test server to test server, getting reviewed, then pushing code to production. many changes are developed concurrently by many developer, and pushed to public server.  I'm wondering if processes wire could adapt to a similar work flow. Being able to export database field changes from one server to another, or page changes from one server to another.

I realize that this would have to be done with care and a some custom modules will have to be written. One thought i had was to be able to export part of the process wire tree from one server to there other, and if there are changes ask, if they should be overwritten.  Not sure if SQL or API would be the best way to go (or a mix). Any one who has experience with exports please let me know what your thoughts are on this, or if its even worth the effort. 

my other thought is to propose an alternative workflow, where databases changes don't move between servers as much as code (which could be possible) but its a cultural shift and I would love to hear what others are doing. 

What are the problem areas with exporting/importing sections of the page tree between servers? will repeaters give issues do to how they are stored in the DB, will that new tables feild move between pages with ease. 

My other thought was to be able to export DB schema changes or field changes.  Again not sure if API or direct DB access would be the best way. Also not sure how friendly pages and fields are about being moved from one server to another, it might be a big can of worms, so I am asking before being the one who gets stuck with the can.

[adrian]

Check out the Migrator module: https://github.com/adrianbj/ProcessMigrator

At the moment I still strongly recommend testing the migration to a test PW installation before running the import to your production install, but it has all sorts of options for migrating content from dev to live, including a new feature during export which allows you to export only those pages that have changed since a specified date/time.

[Neeks]

adrian I can see you put a lot of love into that module. looks really promising. It might be just what i've been looking for.