On 9/20/08, Gregor Ebersberg <[EMAIL PROTECTED]> wrote: > Hi, > Thank you for your answers, also for the parts I do not quote here. However, > I > would like to concentrate on this bit. > > On Saturday 20 September 2008 03:04:39 pm [EMAIL PROTECTED] wrote: > > > Is there a easy way to just use lenya as is and have the visitors of my > > > web site accessing content as if it where made from static html > > > documents? > > Lenya's primary use is WYSIWYG editing of (X)HTML documents. Is this > > not obvious from the "default" Publication? > > Yes, the 'default' publication looks like that. However, I hoped to learn to > use a content management system when I started to spend my time on Lenya. > Therefore I hoped that Lenya would not only do WYSIWYG editing of (X)HTML > documents but also manage the workflow. Actually it does, from what I saw. > However, I hoped the workflow would ultimately lead to output that is ready > to be shown on a web site. I'm still sure Lenya can do that, since there are > sites using lenya and you don't see port numbers in the URLs. > > From former answers I now conclude that I need to deploy Lenya in a Tomcat > environment. No easy way to use lenya to that end. But perhaps some one know > still some other way. For example what if I configure in build.sh to use port > 80 instead of 8888 in the Jetty instalation? > > Thank you so much for your time answering me, > Gregor
If using Jetty, the JETTY_PORT setting controls which port is used. The default is 8888 to avoid conflicts with standard Web servers (e.g. Apache httpd) on port 80 and Tomcat's default port 8080. Set JETTY_PORT=80 if Lenya is the only Web server to avoid URLs containing the port number. In Lenya 1.2.5, the JETTY_PORT is set in lenya.sh. In earlier versions and in Lenya 2.x, JETTY_PORT is an environment variable, although it may still be overridden in lenya.sh. What benefits are you expecting from running Lenya in Tomcat? The primary benefit of Tomcat over Jetty is hot reloading of Java classes -- more useful for development than production. The other benefit is for businesses where adding a servlet to Tomcat is easier than adding a new program (usually due to lengthy approval processes rather than any technical issues.) Lenya in Tomcat shares the JVM with other applications, sometimes creating library conflicts (specifically Xalan.) We use Apache httpd on port 80 proxying to Lenya on another port firewalled from the Internet. For upgrades and new websites, we create new instances of Lenya, test, then just adjust the httpd configuration. We currently use virtual servers, but integrating Lenya pages using the URL path would be almost as easy. One advantage is we remove the publication name from external URLs. As a CMS, Lenya natively controls workflow; you do not need Tomcat to use this feature. According to the Lenya 2.0 website, one- and two-step approvals and email notifications are included. The "default" Publication required one approval before publishing HTML pages. Maybe you can understand the configuration: http://lenya.apache.org/docu20/reference/resource-types.html#N100B5 (which refers to the Lenya 1.2 documentation.) I apologize for my limited knowledge of Lenya 2.x. Our production systems are running Lenya 1.2.5. My development work is on a different branch. Many Lenya 2.x devs are more active on business days. solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
