Thorsten Scherler wrote: > On Wed, 2008-01-16 at 14:35 +0100, Jörn Nettingsmeier wrote: > ... >> thorsten, i'm not too familiar with apache.org's security policy - would >> the following be acceptable?: >> >> a lenya server runs on zones. every doc contributor gets access. to >> reduce headache and discourage jokesters, ssl is mandatory. >> >> a cronjob on another machine will wget -r the live area of the zones >> server every hour or so and copy the stuff into a local svn sandbox >> (some minor wizardry would be needed to correctly "svn add" and "delete" >> files, but it shouldn't be too hard). >> when the wget is done, it either "svn commit"s the stuff automatically, >> or a local webserver makes the repo visible as a web site that can be >> inspected by a committer who then triggers a manual update (maybe after >> discussion on the mailing list). > > I just finished a rewrite of Apache Droids a labs project > http://labs.apache.org/labs.html that can do all of the above for us.
need to check that out, but didn't find the time yet. > Regarding the architecture that meets the policy of the ASF AFAIK. good to know. > However the problem of local vs. public editing described by Andreas > remains. > >> alternatively, the content could be wgotten locally and rsync'ed to the >> other machine (i.e. manual push instead of pull at regular intervals) >> > > IMO having the zones server as our docu server with a real case test of > lenya 2.0 is preferable to local editing of our docu till we find a > solution. you mean running lenya.apache.org directly off a jetty? will the infrastructure guys swallow that? as to authoring, maybe i did not make myself all too clear: i definitely want a test case and there would be one common lenya authoring environment on zones, no "local editing" at all. but since zones must not commit to svn for obvious security reasons, we need a third machine. it can then pull the live site from zones via wget and additionally skim the current revisions from the lenya repository on zones (and only the current ones! stacking svn and our own version control will make disk usage explode...) so that we have a backup of the documentation sources in case something goes wrong with zones. then both the live html pages and the raw data are auto-committed to their respective svn branches. -- Jörn Nettingsmeier "One of my most productive days was throwing away 1000 lines of code." - Ken Thompson. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
