- Destinations: Valid ZSyncers to sync to, including port. For example: http://www.myzopesite.com:8080/my_ZSyncer. These can be https urls if you want. If your destination is a ZEO cluster, you should only give the address for a single ZEO client in the cluster, or just give the virtual address presented by your load balancer.
- Log?: Turns on logging
- Logfile: specify the file to log to
- Approval?: Logs the person who synced this, plus comments and approvers name
- Override: if checked will sync with the user specified below. Others will default to the current user.
- User: username to use when override is checked
- Password: password to use when override is checked
- Syncable types: what meta types you want to sync. See below for info.
How to sync
The sync web page shows the difference between a development Zope and one or more other Zopes. It does this by comparing the date stamps on the objects in Zope.
- File: shows the object name in Zope. If this object is a folder, you can click on it to traverse to the lower folder.
- Status: shows the status of the object in relation between the Zopes it will be one of the following terms:
- ok (green): this object is present on both production and development and is in sync
- missing (red): this object is present development but not production, it needs syncing
- extra this (red): object is on production but not development, it needs deleting from production
- out of date (orange): this object is present on both the production and development, but has been changed on development, it needs syncing
- View: takes you to a version on the appropriate server
- Action: perform the highlighted action
- sync: moves the relevant object from the development server to all the production servers
- delete: removes the relevant object from all the production servers, development servers are unaffected
- diff: if this object has a document_src you can do diff on it. If your ZSyncer has more than one destination, only the first is used for the diff.
- This should be considered experimental, but it sort of limits the objects that can be synced. You specify the meta types and only those show up.
- However if your list of syncable objects is different between boxes this could generate false results. For example, the server has
Foo in syncable types, but the destination doesnt. If thats the case a object type
Foo will show up as missing on the destination because it the
Foo type object did not show up on the server.
- Also if you export a folderish object, all the objects in it are moved not just the syncable types. This is because of the way Zope generates export files.
- Let me know if this makes it a mess.
Versions are respected, if you have made changes in a version they will not be synce'd until committed
If you sync a folder, it will sync all the items in that folder.
If you change an object in a folder, that folder does not become out of date. However if you add or delete objects the immediate parent folder becomes out of date.