Support/Comments for Provisioner 1.7-beta

Check that the directory /assets/components/provisioner/tmp is writeable by your webserver, it should contain small files that CURL uses on every login, if this is the fault here then its a little bug I need to fix.

On another server I found that I could provision fine - except for files. The permissions on the provisioner folder won’t let me change the permissions on the folder itself, or (easily) create folders within the assets/components/provisioner structure. Even after creating mirror-name folders it won’t let me provision.

The perms on the Provisioner folder for file imports allows your webserver to write to it so it can create files on import, you can change this to what you like if you wish then other users can write into this. Its not really meant to be written into from outside Provisioner itself. Provisioner doesn’t enforce anything here, if your on linux say you can change the perms as you see fit.

Hi,

Nice work with provisioner! I’d like to help development as I am looking to migrate content from an Evolution site to a Revolution site. Provisioner seems to be the best upgrade path I could find. I know the modX team is supposed to be developing an upgrade tool but until then it seems that Provisioner is the best we can do.

I have a few questions:

Is there a recommended order for migrating assets? For instance, should you do Templates, TVs, Snippets, Chunks, and then Resources? Does any order offer any benefits?

I found that with one import I have done, Resources retained the old template IDs, but the templates were given new id’s when they were imported so all of the relationships were broken.

Additionally, the published fields were not handled correctly. It does seem to have correctly modified most of the syntax issues.

Can you supply any recommendation for how to use this tool. It would be nice to build this tool out, and it seems if we could pool resources (modX team, you, me, others) that we could develop a much more full featured migration tool.

Thanks!

Hi,

Is there a recommended order for migrating assets?

No, not really, I’ve nort proposed a workflow for this yet as different people will use it differently, maybe I could add this to the docs.

Resources retained the old template IDs,..

Yes, this will happen at the mo because there’s no real intelligence built in to the import. Issue 5 in github has been opened about this type of feature so it will be addressed, for Evolution sites anyway.

the published fields were not handled correctly..

This should be fixed, please open an issue on what you’ve found here in github.

As far as future development goes you’re right that we could add more for Evolution sites, further back in this thread I proposed a full site import on its own tab so we could do this, it just needs doing. This is one reason Provisioner is still in beta, its not quite finished yet, especially now it has Evolution sites added which it didn’t originally.

Please feel free to raise issues, fork the repo in github and work on it.

Just wanted to thank BobRay for writing this. It’s not perfect but it’s a million times better than any script I could have written and a billion times better than trying to move everything from our Evo install by hand. It would definitely be useful to be able to retain the template var content, but in my situation it wasn’t that hard to write a cleanup script to re-create the association between the imported docs and their image files (stored as a tv).

Nice work - but how to install revogateway in a 0.9.6.3 site? Copying the revogateway directory and its contents to assets/snippets/ doesn’t suffice. What am I missing? (I don’t have shell access.)

Er don’t wish to blow my own trumpet here but

Just wanted to thank BobRay..

was actually me i.e. shamblett.

You should be able to do this on 0.9.6.3, you should end up with a directory structure of /assets/snippets/revogateway, under that you should see an index.php file and a connectors folder.

Provisioner installed in your Revo site should bea ble to connect to this.

Thanks - Provisioner does connect to the 0.9.6.3 site, and it does import from there into Revo. (I had assumed something was missing because I didn’t see anything happen on the Evo site after moving the revogateway files there.)

Btw.: Would it be possible to import all of templates, TVs, chunks, snippets etc. at once rather than one by one (like it is possible with resources inside containers)?

Cheers

There’s an issue raised in github about doing ’smart’ imports from evolution sites, it will be on a new tab, slated for November.