On 05/11/2010 03:29 PM, Christian Lohmaier wrote: > ... But it isn't easy to just throw out everything as OOo is huge > and you never know who else is using parts of it.
Take a snapshot and archive read-only and publish it as a vhost. Then drop the idea of using a CMS because we already have CVS and this has taken long enough that warning flags should have risen. There does not seem to be much information about kenai on the kenai web site. Specifically I do not see either the source code, deb or apt packages, or even developer documentation or user guides. It would be possible to do nearly any formatting, including templates and standardized menus and layouts using nothing more than the existing versioning system (CVS) and Server Side Includes (SSI). > Not to mention the servlets, IZ, Mailinglists, anything that is > dynamic basically. Web sites do not have to be treated as monoliths and many can point out that it is an error to try to do so. It is possible and easy to have Apache2, Lighttpd, or nginx apply different treatment to different directories or different name-based virtual hosts. In Apache it is mod_redirect. That allows the regular, static pages to use CSS+SSI at the same time the script-based or wiki-based services do whatever it is they do however it is that they do it. > That combined with different level of access rights (not all users > see every control available), Is there anything beyond the mailing lists, bug tracker and the wikis which have that problem? /Lars --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
