We use wget to create a static copy of the Daisy CMS on our
internal server, and rsync that over to our public plain web server. Crude, but
efficient. Works as long as you don't have very dynamic content. We use
Google to handle the public site search (which takes a few days to pick up
changes). Syncing two different CMS's sounds like a headache... I would
rather proxy Daisy.
My 2 cents,
Gwen.
Thus far my company has been using Daisy exclusively as a system
for creating PDFs via the book output, but we may now be looking at having
Daisy also function as a content management system for some of our web
content, especially for the purposes of using some of the translation and
language variant options built into Daisy. So my question is this: are there
any users who use Daisy as a back-end CMS but who don't use Daisy to actually
deliver the web content? If so, what kind of interface have you created
between Daisy and whatever CMS you use on the web front
end?
Thanks,
Robert
CONFIDENTIAL
This document and
attachments contain information from Fusion-io, Inc. which is confidential
and/or legally privileged.
The information is intended only for the use of
the individual or entity named on this transmission.
If you are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution or taking of any
action in reliance on the contents of this
emailed information is strictly prohibited, and that the documents should be
returned to Fusion-io, Inc. immediately.
In this regard, if you have
received this email in error, please notify us by return email
immediately.
_______________________________________________
daisy community mailing list
Professional Daisy support:
http://outerthought.org/en/services/daisy/support.htmlmail to:
daisy@...
list information:
http://lists.cocoondev.org/mailman/listinfo/daisy