From dev-return-8268-apmail-stdcxx-dev-archive=stdcxx.apache.org@stdcxx.apache.org Wed Aug 13 20:33:00 2008 Return-Path: Delivered-To: apmail-stdcxx-dev-archive@www.apache.org Received: (qmail 76826 invoked from network); 13 Aug 2008 20:32:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Aug 2008 20:32:59 -0000 Received: (qmail 16911 invoked by uid 500); 13 Aug 2008 20:32:55 -0000 Delivered-To: apmail-stdcxx-dev-archive@stdcxx.apache.org Received: (qmail 16868 invoked by uid 500); 13 Aug 2008 20:32:55 -0000 Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stdcxx.apache.org Delivered-To: mailing list dev@stdcxx.apache.org Received: (qmail 16844 invoked by uid 99); 13 Aug 2008 20:32:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Aug 2008 13:32:55 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of msebor@gmail.com designates 209.85.200.170 as permitted sender) Received: from [209.85.200.170] (HELO wf-out-1314.google.com) (209.85.200.170) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Aug 2008 20:31:58 +0000 Received: by wf-out-1314.google.com with SMTP id 24so135434wfg.2 for ; Wed, 13 Aug 2008 13:32:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=SSL0pV9X5dQWzApFq2qXQv+UpCtv5TFJt0r4EU3Wh7c=; b=hYFY0esZWayAmXtnNIOo6POe1kbAeA6QyAG00AuY680s3PZKeU7nSiv3TU3xcWRhao aLP3RViCNi7u7OGehys6mcuXXaFnLKpLtHpO0OCH5n6Sm/zK8ueej2tniiFVq0Ex6aRd tvO0Qizr0eQ9S7ASM9x2W+Si1Q4B8Xt4zoKNY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=KG3iPIoPsr0Zt6rY+HOvLbjNW91T98xe3kChTk2UzmzVvtJ6XbLSjOzu2LhJ8apLwh zV1ZQlUsZVXk6c0RVM7ztuxgv3W5II26CyX4eGsJY+ek3lPxcIWT3ueX4bLVLjPCfbBV R7YHNwabXoTG7O/6kDlb/0eoa+Hb1XkygNRtU= Received: by 10.142.222.4 with SMTP id u4mr110346wfg.329.1218659545848; Wed, 13 Aug 2008 13:32:25 -0700 (PDT) Received: from localhost.localdomain ( [71.229.200.170]) by mx.google.com with ESMTPS id 28sm1946107wfg.15.2008.08.13.13.32.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 13 Aug 2008 13:32:24 -0700 (PDT) Message-ID: <48A344D5.6060104@gmail.com> Date: Wed, 13 Aug 2008 14:32:21 -0600 From: Martin Sebor User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: dev@stdcxx.apache.org Subject: Re: Website Layout References: <945707.1201827547692.JavaMail.jira@brutus> <63203.124.169.96.181.1201840274.squirrel@www.e-wire.net.au> <47A2B563.2010209@roguewave.com> <001f01c864ab$f3da62e0$0200a8c0@developer> <004101c867f2$16025fa0$0200a8c0@developer> <47A8DD67.5010205@roguewave.com> <005b01c8837b$4c72d7f0$0200a8c0@developer> <003901c8fa91$70a3e410$0200a8c0@developer> <48A0FA86.2090603@gmail.com> <002d01c8fc5e$655a20f0$0200a8c0@developer> <48A1DB05.9000501@gmail.com> <007b01c8fce7$16e217a0$0200a8c0@developer> In-Reply-To: <007b01c8fce7$16e217a0$0200a8c0@developer> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Gavin wrote: > >> -----Original Message----- >> From: Martin Sebor [mailto:msebor@gmail.com] >> Sent: Wednesday, 13 August 2008 4:49 AM >> To: dev@stdcxx.apache.org >> Subject: Re: Website Layout >> >> Gavin wrote: > > > >>> So whilst we are at this level of even-ness (?) it is a good time to >> swap it >>> over and make it live. However, over the next day or two, I will add >>> developer docs on how to go about updating the site, altering/adding >> pages >>> etc.. >>> >>> Let me know what you think. >> Sounds like a plan. >> >> I assume we'll commit just the Forrest sources into Subversion >> and generate the site out of them on people.a.o using a cron >> job, correct? > > Well, I'm sure various projects do things in slightly different ways. > However I would not recommend doing any building on people.a.o , and is not > necessary anyway. > > This is how Forrest, xmlgraphics and a few others do it :- > > 1. Alter xdocs locally to your needs. > 2. svn ci to get sources upto date in svn > 3. locally run 'forrest -f publish.xml build' > 4. locally run 'forrest -f publish.xml deploy' > 5. /x1/www/stdcxx.apache.org svn up > > That's the general gist, more fully, > > Forrest stores its site source files in > > http://svn.apache.org/repos/asf/forrest/trunk/site-author/ > > and the generated site docs go to > > http://svn.apache.org/repos/asf/forrest/site/ > > A cronjob on p.a.o then runs svn up hourly to > /x1/www/forrest.apache.org > > The hourly sync to eos/aurora then picks that up and your updated docs are > then live. > > Again, with xmlgraphics, site source files stored in > > http://svn.apache.org/repos/asf/xmlgraphics/site/ > > and the generated site docs go to > > http://svn.apache.org/repos/asf/xmlgraphics/site/deploy/ > > /x1/www/xmgraphics.apache.org is svn of that deploy location, no idea how > often they run svn up or if it is done manually. Also no idea if they use > forrestbot (steps 2 and 3) or whether they svn ci the generated site, you'd > have to talk to Jeremias about that. > > So , possibly 2 slightly different methods. > > I'm happy to help show the way to Forrests' method. And of course I will > continue to be on this list for any help required afterwards. One thing to > note for others listening, it is necessary to have Apache Forrest installed > on your local machine in order to alter the xdocs, test locally, build and > then deploy. > > There is a renewed talk on infra lists about having a shared zone or > something else where projects can build sites using Forrest/Maven/Anakia > that would be installed on the zone, the idea I guess is that generated > source files would live there and be copied over to various projects > /x1/www/*.a.o/ area. I'm not sure how it would work exactly but I'm > following for now to see how it pans out, or how long it will take. Just > thought I'd mention it, in the meantime we need to do one of the above. I assume you're referring to the thread on Automating parts of the web site publishing process. I've seen the discussion but haven't had time to follow it closely enough to benefit from it. > > So, here's how I see it for stdcxx :- > > Have forrest and site source files where they are currently in > > http://svn.apache.org/repos/asf/stdcxx/site/forrest/ > > Have the generated site files in > > http://svn.apache.org/repos/asf/stdcxx/site/deploy/ > > and 'svn remove' the current content from /site/ > > The above structure will remove the nasty side effect you currently have of > forrest source files viewable on the web (http://stdcxx.apache.org/forrest/) > doesn't look good. > > Then create a cronjob to svn up hourly (or whatever delay you prefer) to > update your /x1/www/stdcxx.apache.org with the updated site files. > > That's about it for now, what do you think? Thanks for the detailed info! The depot structure and the cron job approach sound reasonable (we already have a cron job running to periodically update the existing site). My only concern is the requirement to run Forrest locally on each committer's machine. Do you happen to know the other projects' rationale for checking the generated sites into Subversion instead of generating their sites directly on people.a.o? It seems that since the site is generated from sources that already are in Subversion there should be no reason to version the generated HTML as well, and being able to update the site without having to have Forrest install seems like a significant advantage. But given that most other projects do it differently I suspect I must be missing some significant disadvantages of the "simpler" approach. Is there concern with the overhead o projects running Forrest too often? FWIW, the way I originally set up this project was to generate the Forrest site in: http://people.apache.org/~sebor/stdcxx/forrest-site/ The cron job that does the updating is in: /people.apache.org:/home/sebor/bin/update-site.sh Martin > > Gav... > > >