See also bug 31071 ("Extend the forrest webapp with "lenya" functionality or vice versa").
i'm making this bug a little more visible... if you object, revert.
Should not be a blocker for the release.
Renaming Lenya 1.4 to 2.0
I implemented a class to import the documentation in 2.0-dev: http://lenya.zones.apache.org:9999/docu/authoring/project-information/indexpm.html
The major question is: Do we try to mimic the behaviour of Forrest (maybe by including XSLTs etc. using svn:externals) or do we create our own documentatin publishing concepts? Maybe we can use a combination of both. For instance, the SVN logs could still be published with Forrest - content management doesn't make much sense here.
(In reply to comment #6) > The major question is: Do we try to mimic the behaviour of Forrest (maybe by > including XSLTs etc. using svn:externals) or do we create our own documentatin > publishing concepts? > > Maybe we can use a combination of both. For instance, the SVN logs could still > be published with Forrest - content management doesn't make much sense here. i'm not really qualified to comment, since i still haven't got the point of forrest... to me it's just a huge complication. i'd say let's drop it entirely and hack some showcase doctype for dynamic data into lenya. the data source would be "svn log --xml" (or rather, a file that is created regularly by a unix cron task), and then toss it into an xslt. i have a generic "dynamic data" doctype lying around that basically contains an xquery (i was using eXist, could easily be changed to connect to an SQL db or read a file or whatever) and has an xslt associated to it via a metadata field (this xslt is also stored in the lenya repository). that means i can add new data sources and presentation on-the-fly without re-deploying. wdyt?
(In reply to comment #7) > (In reply to comment #6) > > The major question is: Do we try to mimic the behaviour of Forrest (maybe by > > including XSLTs etc. using svn:externals) or do we create our own documentatin > > publishing concepts? > > > > Maybe we can use a combination of both. For instance, the SVN logs could still > > be published with Forrest - content management doesn't make much sense here. > > i'm not really qualified to comment, since i still haven't got the point of > forrest... to me it's just a huge complication. > i'd say let's drop it entirely and hack some showcase doctype for dynamic data > into lenya. the data source would be "svn log --xml" (or rather, a file that is > created regularly by a unix cron task), and then toss it into an xslt. Maybe we could even use the svn web (http://svn.apache.org/viewvc/lenya/#dirlist) somehow?
(In reply to comment #8) > Maybe we could even use the svn web > (http://svn.apache.org/viewvc/lenya/#dirlist) somehow? > welcome to a world of pain: http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fsvn.apache.org%2Fviewvc%2Flenya%2F%23dirlist
I have added a separate Lenya instance for the docu pub on the zone: http://lenya.zones.apache.org:7777/docu/authoring/index.html I also altered the site structure a bit. It doesn't represent the Forrest site structure 1:1 anymore, so the changes have to be synchronized manually.
As a proof of concept, I exported a part of the site as static HTML: http://lenya.zones.apache.org/docu-preview/index.html The following command was used: wget --cut-dirs=2 -nH -r -e robots=off http://localhost:7777/docu/live/
The next preview version is online: http://lenya.zones.apache.org/docu-preview/index.html The import is pretty complete now. Some little things have to be changed manually. The position of the "Community" node in the sitetree has to be updated. And some site: links haven't been converted. ToDo: - resolve access control issues - backup strategy
At godaddy.com open source projects can get a one-year SSL certificate for free: https://www.godaddy.com/gdshop/ssl/ssl_opensource.asp?se=%2B Should we use this offer?
I have switched to Tomcat for the moment, since I'm not familiar with proxying and SSL with Jetty yet. We can switch back anytime. http://lenya.zones.apache.org:8080/lenya/docu/authoring/index.html
Finished tasks: - simplified CSS, removed transparency from PNGs, kind-of works with IE6 now - provided print view CSS - cleaned up sitemaps and removed obsolete XSLTs ToDo: - install mod_proxy_ajp on the zone - setup the httpd configuration for proxying Unfortunately I can't complete these tasks since I don't have root access.
I exported another preview: http://lenya.zones.apache.org/docu-preview/ Some links point to /externalrefs documents. This has to be fixed, I'll try to find out how.
(In reply to comment #16) > Some links point to /externalrefs documents. This has to be fixed, I'll try to > find out how. Done. I implemented a "Reports" usecase which finds all broken internal links.
(In reply to comment #15) > ToDo: > > - install mod_proxy_ajp on the zone > - setup the httpd configuration for proxying I filed a bug for the infrastructure team requesting the installation of mod_proxy_ajp. I have no idea if and when this will be done. If we want to switch in the near future, I guess we have to use Jetty/Tomcat without proxy.
Hmm, I agree to wait for infrastructure can take for ages. We should do it ourself but that means our Chair need to give us the rights.
I configured mod_proxy: https://lenya.zones.apache.org/cms/docu/authoring/index.html Tomcat accepts only connections from 127.0.0.1 (using a valve in the context declaration), so SSL is enforced. I used a little trick, though, to avoid adding SSL handling to Tomcat: A https:// proxy URL is configured for non-SSL connections. If someone knows a better way, I'm grateful for any hints.
Now the static export command is wget -t 1 -T 5 --no-check-certificate -p --cut-dirs=3 -nH -r -e robots=off https://localhost/cms/docu/live/index.html Connecting to https://lenya.zones.apache.org doesn't work (maybe due to virtual IP issues). At some point, wget tries to request a page from this host (no idea why), therefore the timeout parameters.
The API links in the sitetree don't work yet.
(In reply to comment #22) > The API links in the sitetree don't work yet. That's fixed.
I would say that we've succeeded in using Lenya to publish our own website, so I am closing.