You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Jeff Turner <je...@apache.org> on 2003/08/08 17:20:14 UTC

Forrestbot (Re: cvs commit: incubator-site/build/site/skin breadcrumbs.js)

On Fri, Aug 08, 2003 at 02:18:57PM +0200, Sander Striker wrote:
> > From: jefft@apache.org [mailto:jefft@apache.org]
> > Sent: Friday, August 08, 2003 2:06 PM
> 
> > jefft       2003/08/08 05:06:01
> > 
> >   Modified:    build/site/skin breadcrumbs.js
> >   Log:
> >   Automatic publish at Fri Aug  8 14:05:59 CEST 2003 from http://forrestbot.cocoondev.org.
> 
> ?

http://forrestbot.cocoondev.org is a webapp that automates part of the
update process for Forrest-using sites.  Every few hours it fetches the
latest site XML and renders it (optionally using the latest Forrest).
Users (some anyway - see below) can also manually trigger a refresh, and
trigger a commit (with my uid) to a module, in this case
incubator-site/build/site/.  Forrestbot has proved very handy for
xml-site, which is now 155M and consequently takes ages to update over a
modem connection.  It also saves developers from having to deal with
Forrest.  As long as the docs validate (using any tool), they can be
checked in and published through the webapp.  Separation of content from
presentation and all that.

If there's people who regularly update the site and would like to use the
system, please let me or forrest-dev@ know.  The site's refresh/update
facility is password-protected to prevent random visitors from wasting
the server's CPU/bandwidth.  It's not really meant to be a security
measure - if anyone guessed the password, the worst they could do is
synch the XML and rendered pages.  The server process is running under
ssh-agent+passphrase.

> >   ===================================================================
> >   RCS file: /home/cvs/incubator-site/build/site/skin/breadcrumbs.js,v
> >   retrieving revision 1.5
> >   retrieving revision 1.6
> >   diff -u -r1.5 -r1.6
> >   --- breadcrumbs.js	7 Aug 2003 21:38:33 -0000	1.5
> >   +++ breadcrumbs.js	8 Aug 2003 12:06:01 -0000	1.6
> >   @@ -4,7 +4,7 @@
> >                       The Apache Software License, Version 1.1
> >     ============================================================================
> >    
> >   - Copyright (C) 2002-2003 The Apache Software Foundation. All rights reserved.
> >   + Copyright (C) 2002 The Apache Software Foundation. All rights reserved.
> 
> What's this?

Ah, it's a bug in the forrestbot.  Some tokens are being inherited from
the xml-site module, instead of incubator-site.  I hadn't noticed this
before, because all xml.apache.org sites share mostly the same tokens.
I'll look into it tomorrow.  I've fixed it in the meanwhile by
regenerating the site by hand.


--Jeff

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Forrestbot (Re: cvs commit: incubator-site/build/site/skin breadcrumbs.js)

Posted by Jeff Turner <je...@apache.org>.
On Fri, Aug 08, 2003 at 09:41:11AM -0700, Greg Stein wrote:
> On Sat, Aug 09, 2003 at 01:20:14AM +1000, Jeff Turner wrote:
> >...
> > > >   +++ breadcrumbs.js	8 Aug 2003 12:06:01 -0000	1.6
> > > >   @@ -4,7 +4,7 @@
> > > >                       The Apache Software License, Version 1.1
> > > >     ============================================================================
> > > >    
> > > >   - Copyright (C) 2002-2003 The Apache Software Foundation. All rights reserved.
> > > >   + Copyright (C) 2002 The Apache Software Foundation. All rights reserved.
> > > 
> > > What's this?
> > 
> > Ah, it's a bug in the forrestbot.  Some tokens are being inherited from
> > the xml-site module, instead of incubator-site.  I hadn't noticed this
> > before, because all xml.apache.org sites share mostly the same tokens.
> > I'll look into it tomorrow.  I've fixed it in the meanwhile by
> > regenerating the site by hand.
> 
> It seems there is some kind of competing base going on here. I regenerated
> the site a couple days ago and checked in the whole mess. Then, yesterday,
> the autopublish checked in some changes which reverted a lot of that.
> 
> For example, in build/site/bylaws.html, my regeneration made the META header
> tag specify UTF-8, but then the autopublish reverted it back to ISO-8859-1.
> 
> It sounds like the autopublisher is using some old version of Forrest. I'm
> working from HEAD. I also have no local modifications or user-specific
> configuration/state (since I never had forrest on this box until a few days
> ago).

Yes, the forrestbot site is using Forrest 0.4.  Various changes (like the
iso-8859-1 -> UTF-8 change) were made in the 5 months since 0.4.  Nothing
very significant though.  It sounds like most people doing doc updates
are happy using CVS Forrest (it's about 70% faster), so I'll change the
forrestbot site.

--Jeff

> 
> Cheers,
> -g
> 
> -- 
> Greg Stein, http://www.lyra.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Forrestbot (Re: cvs commit: incubator-site/build/site/skin breadcrumbs.js)

Posted by Greg Stein <gs...@lyra.org>.
On Sat, Aug 09, 2003 at 01:20:14AM +1000, Jeff Turner wrote:
>...
> > >   +++ breadcrumbs.js	8 Aug 2003 12:06:01 -0000	1.6
> > >   @@ -4,7 +4,7 @@
> > >                       The Apache Software License, Version 1.1
> > >     ============================================================================
> > >    
> > >   - Copyright (C) 2002-2003 The Apache Software Foundation. All rights reserved.
> > >   + Copyright (C) 2002 The Apache Software Foundation. All rights reserved.
> > 
> > What's this?
> 
> Ah, it's a bug in the forrestbot.  Some tokens are being inherited from
> the xml-site module, instead of incubator-site.  I hadn't noticed this
> before, because all xml.apache.org sites share mostly the same tokens.
> I'll look into it tomorrow.  I've fixed it in the meanwhile by
> regenerating the site by hand.

It seems there is some kind of competing base going on here. I regenerated
the site a couple days ago and checked in the whole mess. Then, yesterday,
the autopublish checked in some changes which reverted a lot of that.

For example, in build/site/bylaws.html, my regeneration made the META header
tag specify UTF-8, but then the autopublish reverted it back to ISO-8859-1.

It sounds like the autopublisher is using some old version of Forrest. I'm
working from HEAD. I also have no local modifications or user-specific
configuration/state (since I never had forrest on this box until a few days
ago).

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Forrestbot (Re: cvs commit: incubator-site/build/site/skin breadcrumbs.js)

Posted by Berin Lautenbach <be...@ozemail.com.au>.
Jeff Turner wrote:
> incubator-site/build/site/.  Forrestbot has proved very handy for
> xml-site, which is now 155M and consequently takes ages to update over a
> modem connection.  It also saves developers from having to deal with
> Forrest.  As long as the docs validate (using any tool), they can be
> checked in and published through the webapp.  Separation of content from
> presentation and all that.


Given the sites are getting so big (xml-site > 150M is a bit scary), is 
a cvs sync still the right way to do it?  Storing binary files (PDF) in 
the cvs repository is going to get very big if any files get frequently 
changed (e.g. news in xml.apache.org), and it doesn't really seem 
necessary if we can regenerate any version of the pdf from the xml 
source of the same version.

Should we be looing at modifying the forrest portions of the site so 
that forrestbot pushes them into the web server in another way and thus 
take the generated docs out of CVS?

Or could we run a script on the web server that checks if the source has 
changed and tries to rebuild the site if it determines it has? 
(Effectively run forrestbot on the site - don't know what 
infrastructure@ would feel about that.)

Cheers,
	Berin


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org