Adds ftw.bridge support to plone.
The ftw.bridge tools are used for communication between several Plone instances. It is also possible to communicate with other web services. Requests between web services are proxied through the ftw.bridge.proxy. This makes it possible to move or reconfigure certain dependent webservices (clients) only by reconfiguring the proxy. The clients do not know where other target clients are located - they only communicate with the proxy directly, which forwards the requests to the target client.
ftw.bridge.client integrates ftw.bridge support into Plone. It provides tools and utilities for communication and authentication.
A installation of ftw.bridge.proxy is required.
Add ftw.bridge.client to your eggs in the buildout configuration:
[instance] eggs += ftw.bridge.client
Configure the ftw.bridge.proxy data as environment variables:
[instance] environment-vars += bridge_url http://localhost:1234/proxy bridge_ips 127.0.0.1, 192.168.1.10 bridge_client_id workspace
Install the generic setup profile. This registers the portlet and installs a PAS plugin.
The configuration options are set using environment variables:
Runs with Plone \(4.1\), \(4.2\) or \(4.3\).
This package is copyright by 4teamwork.
ftw.bridge.client is licensed under GNU General Public License, version 2.
Implement uninstall profile. [jone]
Use ftw.profilehook instead of custom import steps (setuphandlers). [jone]
ftw.solr compatibility hacks
Watcher portlet: fix encoding problem when having discussion items. [jone]