Bernd Fondermann ha scritto: > Noel J. Bergman wrote: >>> Confluence is not backuped and properly QOS'ed. >> >> There are issues, but the pages have to be statically exported and >> served up >> by httpd, which helps with QoS. If Confluence self-immolates, at least >> we'll have what it generated. > > Interesting. Doesn't sound like C. was a better solution for the > intended purpose compared to what we have now. > > Bernd
Why? You just login to confluence, apply your changes using a web based visual editor, submit and wait. Confluence does everything else. The export to static html is automatic. The copy from the static export to the minotaur folder can be done via cron as explained here: http://cwiki.apache.org/CWIKI/#Index-Canweusetheautoexportsiteaspartofourmainwebsite%3F And according to cwiki it is also being backed up: http://cwiki.apache.org/CWIKI/#Index-Isthissitebackedup%3F Furthermore we can keep committing the generated (or even the xml, as confluence can export also xml files) to our svn from time to time (maybe only when we do release, skipping the full workflow for minor changes/news and other edits) If you want more details on how Confluence would work I can try explaining it better. You can see a live example of home (including news) managed by mina using Confluence: http://mina.apache.org/ News are simple wiki pages editable via Confluence in this pages: http://cwiki.apache.org.dontlink.cwiki.pages/confluence/display/MINA/2007/08/12/Apache+MINA+1.0.5+and+1.1.2+Released (of course you have to remove the dontlink.cwiki.pages host part) Confluence also provides an RSS feed that could be made static using the technique described by Noel and Sam Ruby (until the Confluence's auto export plugin won't support this: export of css+rss to static resources is already in their todo: http://could.it/bugs/browse/EXP-6 ). Stefano
