I am following the advanced help docs, and it doesn't match the interface -- it seems to be out of date.

I've created a profile, enabled yamm client and server on different hosts, created a view, and ready to push an update, but there's nowhere to run the push.

The page admin/objects/yamm_sync_profile/MY-OBJECT is empty.
There is a "edit" tab and a "export" tab, but no options to actually perform the migration.

This is a bug in the documentation, if not a bug in code.
Please help, thanks!

Comments

aaronbauman’s picture

aaronbauman
he/him
commented
Title: Documentation out of date - documentation bug or code bug? » Documentation update please

it seems that for some reason after creating the synch job and editing settings, i ended up at admin/objects/yamm_sync_all/MY-OBJECT instead of where I should have been, admin/yamm/client/MY-OBJECT

This is a minor issue, but confusing UX.

Additionally, there is no documentation about various things:
* how to configure Datasync
* what is supposed to happen after a job is "pushed"
* drush utilities

When I figure out how this stuff works, I'll give a whack at documentation.
Until then, any help would be much appreciated.

pounard’s picture

pounard
Primary language French
commented

Actually the latest version is under active developement, I may help you as as soon as things began to become stable. Are you on IRC ? I could help you there if you want.

Here are some quick answers:

how to configure Datasync

DataSync is awfull to configure, that's why in recent version we abandonned it and use daemoncli instead, which does almost the same stuff (more simple though) but does not need neither a complex configuration neither core patches.

what is supposed to happen after a job is "pushed"

The server pushes a synchronization order to client (this is an XML-RPC call). Then, depending on the client response two possibilities:

The client returns an error
It can happen for many reasons, network unreachable, client already being synchronizing with the server, the server did not send the right credentials, ... Then the server just does nothing.
The client accepts the transaction
The server creates a "yamm transaction" row in database, using a unique identifier sent to client and set its state as "awaiting for pull". The client, sometimes later (depending on cron, DataSync or DeamonCli configuration) will use the PHP CLI deamon to do series of XML-RPC "pull" calls. This is a "push/pull mecanism": the server push an order, client accepts and then pull content from server. Each XML-RPC call will fetch some amount of content and this content's dependencies, and it will continue until the server says "I'm done sending you content".

drush utilities

Actually drush integration is broken right now, I should have disabled it. But it can help you send orders to client from the server without clicking in the UI, that's all about it.

pounard’s picture

pounard
Primary language French
commented
Status: Active » Closed (won't fix)

Very outdated module.