Hello list! On Sunday 21 September 2008 01:43:22 pm [EMAIL PROTECTED] wrote: > Most devs like Tomcat reloading Java classes without restarting Lenya > while developing. I develop using Jetty, and am constantly restarting > Lenya. > > For production. Jetty is easier than Tomcat for maintenance: > - easier multiple instances of Lenya. > - separate configuration of each instance. > - easier configuration of the proxy since each instance uses a different > port. - each Lenya instance in a separate JVM. The MLs contain debates > whether this is better or worse for process and memory management, but > it definitely avoids Java class conflicts. > - less technology (since you do not need to install/configure/use Tomcat.) > > I was surprised you felt Tomcat was necessary. The installation > instructions at: > http://lenya.apache.org/docu20/installation20/install20.html > explain the standalone implementation first. What caused you to think > that Tomcat was needed? We are always seeking to improve the > documentation. Should we add a line stating, "We recommend the Jetty > standalone installation for beginners."?
That is certainly a way to respond, if this is an issue at all. However, my problem was even more rooted in my lack of knowledge: I had to look up what Jetty is. And I did so only after encountering the term in some of the answers on this list. So same on me but only briefly. I would opt for explaining all names in the documentation text (and not relaying on the user following a link, if you think you can take advantage of hypertext) iff (if and only if) the name is crucial in the understanding of the documentation text's meaning. In the case of >Jetty<, I needed to be aware that Jetty provides http server functionality to understand that I don't need Tomcat with Apache altogether. On the other hand, if I understood this bit, this also means that I have to abandon my Apache server to use Lenya in a ready-made out-of-the-box fashion (and it is still a question whether someone else finds this useful). Perhaps abandoning Apache is improbable for the average newbie that the Lenya community is poised to convince of Lenya's value. Perhaps it's much easier to explain explicitly in the documentation that the port numbers in the URLs will vanish once Lenya is properly and permanently installed on the new user's host. And meanwhile new users have to endure the port numbers in the URLs but, of course, need not worry about them since they vanish if the new user decides to install Lenya permanently. I even thought all visitors need to go through the start screen, e.g. the one set up as the main demo site at http://lenya.zones.apache.org:9999/index.html (linked in the second line of text on http://lenya.apache.org . Is it possible to first lead the visitors of the Lenya home page to a working example of content served by a Jetty instance including a prominant link to the Lenya management of that content? (Of course since the transition from forrest to Lenya, as far as I read, the whole content is managed by Lenya, but new visitors can only learn from what they are aware of. > The following is provided more to explain possibilities with Lenya > than suggest this is the best implementation. Below is an excerpt > from our Apache httpd configuration for proxying to Lenya 1.2. We > only use Kupu for editing so more might be needed for other editors. > Lenya 2.x would require testing and probably many changes. > ProxyPassReverseCookieDomain requires at least Apache httpd 2.1. > > Our implementation requires login to the main website > (www.example.com) before entering edit mode (on edit.example.com). > Accessing the edit server without logging in returns a blank page. > The main website has "edit" links when a visitor has the rights to > edit a page. > > The session Cookies are at the domain level so sessions work for both > server names. The default domain server name (http://example.com) > would not work as the Cookies would not be shared. (We Redirect the > default domain server name to add "www.".) > > The Publication name is removed from URLs. The only clues that the > website is running Lenya are: > - the META Generator Header. (Our goal was not to hide that we are > using Lenya, just have concise URLs.) > - the language (e.g. "_en") in every page name. > - the "lenya.usecase" querystring parameter in the Register/Login, > Contact, Sitemap, and Search URLs. (Lenya 2 uses similar syntax for > "lenya.module". My development version does not require the > querystring for basic functionality.) > > <VirtualHost *> > ServerName edit.example.com > RewriteEngine On > RewriteRule ^/$ http://127.0.0.1:8888/myPublication/authoring/$1 > [P] RewriteRule ^/images/(.*)$ > http://127.0.0.1:8888/myPublication/authoring/images/$1 [P] > RewriteRule ^/css/(.*)$ > http://127.0.0.1:8888/myPublication/authoring/css/$1 [P] > RewriteRule ^/(.*)$ http://127.0.0.1:8888/$1 [P] > ProxyPassReverseCookieDomain 127.0.0.1 example.com > ProxyPassReverse / http://127.0.0.1:8888/ > </VirtualHost> > <VirtualHost *> > ServerName www.example.com > RewriteEngine On > RewriteRule ^/edit.example.com/(.*)$ /$1 > RewriteRule ^/myPublication/live/(.*)$ > http://127.0.0.1:8888/myPublication/live/$1 [P] > RewriteRule ^/myPublication/authoring/(.*)$ > http://127.0.0.1:8888/myPublication/live/$1 [P] > RewriteRule ^/lenya/(.*)$ http://127.0.0.1:8888/lenya/$1 [P] > RewriteRule ^/kupu/(.*)$ http://127.0.0.1:8888/kupu/$1 [P] > RewriteRule ^/(.*)$ http://127.0.0.1:8888/myPublication/live/$1 [P] > ProxyMaxForwards 2 > ProxyPassReverseCookieDomain 127.0.0.1 example.com > ProxyPassReverse / http://127.0.0.1:8888/myPublication/live/ > </VirtualHost> I appreciate details very much and certainly this many helpful lines! (SO I might be off for quite some time to try some of the above on my own. Thank you so much, Gregor --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
