On Wed, 2005-05-25 at 10:31 -0400, Gregor J. Rothfuss wrote: > J. Wolfgang Kaltz wrote: > > > Do you mean that we would edit content in Lenya, which stores it in the > > filesystem, then do a static export of the "site", and store the > > resulting html in the svn ? If so, I guess the Cocoon ReadWriteToSVN > > wouldn't come into play ? > > no we would no longer store the rendered html in svn, but only the > source documents > > > Or do you mean, the content we edit in Lenya is directly stored in SVN, > > as described in the Cocoon Wiki ? In this case, do you know if it would > > be enough for us to alter the publication's sitemap or would we need > > some custom Java code as well ? > > In this case IIUC the static export would happen e.g. once a day, and > > access a running Lenya instance, which in turn accesses svn for content. > > i suppose at first we could store both a copy locally in content/ and > save a copy to svn using the approach described in the wiki. i'm > interested in the easiest way possible to make this work
The thing is that on site-dev we are discussing about a central place for the staging. If we do it "our" way (wget,...) we will have to change that again in a couple of days/weeks/months. Due to the fact, that we have all our docs now in xdocs format I reckon we should keep them in this format and I will modify some forrest properties to export this docs again into the site-svn. I mean editing,... in lenya and the rest like always in forrest (using the live tree of the lenya instance). WDYT? salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
