Andreas Hartmann wrote:
Jörn Nettingsmeier schrieb:
Andreas Hartmann wrote:
There are many issues to be resolved before we can consider replacing
our website:
- Can we host it on the zones server and point lenya.apache.org there?
- editing and publishing workflow, permissions
- management of SVN logs
- caching / static export
let's get the thing rolling on zones and do a static wget -l -r nightly
to apache.org. zones is a little bit too fragile to have it serve the
main website imho, and i think infrastructure would frown on the extra
bandwidth usage. (and if ever, god forbid, the lenya servlet should
barf, our marketing would go to pieces :-D)
A static export sounds good. Maybe we can trigger it automatically by
the publishing usecase someday. It's a pity that we can't showcase our
nice search engine integration, though :)
well, i think we can always justify to divert a few pages to zones that
rely on dynamic lenya features. it means an extra publication on zones,
but it would be a marvellous test case for our proxying code, so that
all links point back to the static web server.
--
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]
