Continuous integration, profile management, etc. -- redux

[rajo]

Hi all,

I have been looking for a way to manage deployment of new sites, as well as versioning of the pw data model on sites already deployed, working with teams, etc. I've enjoyed the discussion on a few threads :

https://processwire.com/talk/topic/6707-update-live-site-from-staging-server

https://processwire.com/talk/topic/2975-team-development

https://processwire.com/talk/topic/2117-continuous-integration-of-field-and-template-changes

but so far, I have not found what I'm looking for, so I built two tools and have put them on my newbie github site for all to use and/or peruse.  I hope they are relevant to this community.  They are crude and only have been exercised in my relatively finite world of Windows/apache dev.

See  https://github.com/jeanrajotte/schlepwire and https://github.com/jeanrajotte/upgradewire

Both "apps" are not designed to be modules, integrated into pw, but rather external simple apps serving their specific purposes, possibly usable in automated build systems via curl, for example.

There's a bit of a diatribe in the upgradewire README.md about the goodness of keeping the model in version-able source files, as distinct from operating the pw admin to maintain fields and templates, even if these changes are being recorded, as mindplay.dk seems to be doing.  That's really the philosophical thrust behind these efforts.  

It's a beginning. I hope it's of interest here.

Again, thank you for this superb framework and this generous community.

Jean

[apeisa]

Very interesting tools, especially the upgradewire. Did I understand correctly, when using upgradewire, you don't actually use the templates & fields through admin at all, but always create new xx_xx_xx.php script, that runs all the required field, template and page changes?

[rajo]

Very interesting tools, especially the upgradewire. Did I understand correctly, when using upgradewire, you don't actually use the templates & fields through admin at all, but always create new xx_xx_xx.php script, that runs all the required field, template and page changes?

That's right, apeisa. While I'm learning the metamodel of templates and fields, I use the admin to create new ones, then I look in the database, in the Fields and Teamplates and other tables to see what was written by the admin, then I emulate that in my scripts.  But in the long run, once I've "mastered" the models, I only create those xx_xx_xx.php scripts and they modify the fields and templates and document the evolution of the site in a repeatable, transportable way.  

Thanks for your interest.