You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Nicola Ken Barozzi <ni...@apache.org> on 2003/06/29 20:04:06 UTC
[RT] Using Lenya with Forrest for ASF sites
Hi guys! I'm starting a RT==RandomThought about using Lenya with Forrest.
Scenario
----------
Any OS product must recieve good beta testing. It's an integral part of
it, and closes the feedback loop.
The Apache Software Foundation Projects are an excellent testbed, because:
1 - high load
2 - many users
3 - very good admins
4 - many users are advanced developers
The Apache HTTPD server is used to drive the ASF website, and this makes
it a good showcase and also a good mean of testing it.
Apache James wants to be the ASF mail server.
Cocoon would love to become the webapp server for publishing.
Forrest was in fact initially an implememtation based on Cocoon to make
the website for Apache and other OS projects.
Lenya? Well, conceptually Lenya fits in very well in this scenario, as
it adds CMS capability to Cocoon, which is what we still need in our
infrastructure.
Needs
-------
What are the needs AFAIK that Lenya has to fulfill?
Well, it has to make it possible to edit pages using the browser, and
add publishing workflow to the picture. But ok, this is standard.
What I don't have a precise idea on how to do it is integration with CVS
and with Forrest. Users must be able to generate the site using Forrest
locally, and also change the site locally and synch with CVS as they do
now. AFAIK though this breaks the workflow...
Wait, but we need not stick to CVS, as SVN can also be used. SubVersion
is WebDav enabled, if this can help you.
In practice, what would you guys suggest doing for integrating Lenya in
Forrest and making it all work with CVS or SVN?
I want to install Lenya+Forrest combo on a Server, configure it to use a
repository, and have changes come in both via SVN or the web interface.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: [RT] Using Lenya with Forrest for ASF sites
Posted by Michael Wechner <mi...@apache.org>.
Nicola Ken Barozzi wrote:
>
> Hi guys! I'm starting a RT==RandomThought about using Lenya with Forrest.
>
> Scenario
> ----------
>
> Any OS product must recieve good beta testing. It's an integral part
> of it, and closes the feedback loop.
>
> The Apache Software Foundation Projects are an excellent testbed,
> because:
>
> 1 - high load
> 2 - many users
> 3 - very good admins
> 4 - many users are advanced developers
>
> The Apache HTTPD server is used to drive the ASF website, and this
> makes it a good showcase and also a good mean of testing it.
>
> Apache James wants to be the ASF mail server.
> Cocoon would love to become the webapp server for publishing.
> Forrest was in fact initially an implememtation based on Cocoon to
> make the website for Apache and other OS projects.
>
> Lenya? Well, conceptually Lenya fits in very well in this scenario, as
> it adds CMS capability to Cocoon, which is what we still need in our
> infrastructure.
>
> Needs
> -------
>
> What are the needs AFAIK that Lenya has to fulfill?
> Well, it has to make it possible to edit pages using the browser, and
> add publishing workflow to the picture. But ok, this is standard.
>
> What I don't have a precise idea on how to do it is integration with
> CVS and with Forrest.
We already started the integration with Forrest re the Lenya
documentation (the "docs-new" Lenya publication), but
yes, it needs more work ...
> Users must be able to generate the site using Forrest locally, and
> also change the site locally and synch with CVS as they do now. AFAIK
> though this breaks the workflow...
if we are using just one CVS workspace with Lenya on top of it, acting
as a browser based CVS Client, then it shouldn't
be a problem.
If some people want to use their own CVS workspace with other CVS
Clients (Command line, emacs, ....)
then it will be difficult, although we could use the email notification
of CVS commit to try syncronization with the Lenya
CVS workspace, but I guess it would be a bit akward
>
>
> Wait, but we need not stick to CVS, as SVN can also be used.
> SubVersion is WebDav enabled, if this can help you.
yes I think WebDAV definitely helps, especially deltaV. I also talked
about that with Gianugo and Guido at OSCOM 3.
>
>
> In practice, what would you guys suggest doing for integrating Lenya
> in Forrest and making it all work with CVS or SVN?
In the case of the Lenya documentation we tried to merge Forrest and
Lenya, but it's difficult with regard to maintenance
of the code. In the meantine I would say it might make more sense to
give each of them (Forrest and Lenya) a context
on their own, whereas Lenya is pointing into the Forrest context and
offering the CMS capability.
>
>
> I want to install Lenya+Forrest combo on a Server, configure it to use
> a repository, and have changes come in both via SVN or the web interface.
sure, let's start :-) I think that is the only way how we get started
and personally I would love to do something like this.
Thanks
Michael
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
JSR 147 (Re: [RT] Using Lenya with Forrest for ASF sites)
Posted by Andreas Kuckartz <A....@ping.de>.
> does SoftwareAG want to implement (http://jcp.org/en/jsr/detail?id=147)
> into Slide?
I have appended an announcement sent by Juergen Pill (Software AG) to the
slide-dev list in February 2003.
Andreas
Re: [RT] Using Lenya with Forrest for ASF sites
Posted by Guido Casper <gc...@s-und-n.de>.
Michael Wechner wrote:
<snip/>
> btw, have you been able to make CVSSource by Sylvain work on
> Cocoon2.1?
No, I am myself not particularly interested in CVSSource at this point.
<snip/>
>>> I can see the power of a WebDAVSource. Do you think the WebDAV
>>> implementation of Slide can be reused
>>> for a WebDAVSource?
>>>
>>>
>>
>> Basically there are now 3 implementations to choose from in Slide's
>> CVS.
>> -The JSR 170 proposal which sits on top of a WebDAV transport layer
>> IIUC.
>> -The JSR 147 proposal which Software AG currently pushes to
>> implement.
>>
> does SoftwareAG want to implement
> (http://jcp.org/en/jsr/detail?id=147)
> into Slide?
>
>> -The "old" Slide WebDAV client library which is an extension to
>> commons-http and would be my first choice currently since it's the
>> most stable.
>>
>
> you mean Side's WebDAV servlet?
>
No, I meant only the available implementations of WebDAV client side
libraries for a potential WebDAVSource implementation.
Guido
--
Guido Casper
-------------------------------------------------
S&N AG, Open Source Competence Center
Tel.: +49-5251-1581-87
Klingenderstr. 5 mailto:gcasper@s-und-n.de
D-33100 Paderborn http://www.s-und-n.de
-------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: [RT] Using Lenya with Forrest for ASF sites
Posted by Michael Wechner <mi...@apache.org>.
Guido Casper wrote:
>Michael Wechner wrote:
>
>
>>Guido Casper wrote:
>>
>>
>>
>>>I don't understand how you want to use Lenya for ASF sites,
>>>
>>>
>>>
>>I think the goal would be to simplify the "updating" process
>>
>>http://cocoon.apache.org/lenya/community/website-update.html
>>
>>which basically means certain committers have the module
>>"project-site" within their
>>local CVS workspace. Checkin means in this sense "ready to publish"
>>and
>>as soon as
>>sombody is updating the corresponding module on daedalus one is
>>actually publishing the data.
>>
>>
>
>Ah, so the wanted solution would not be Forrest --> Lenya but Lenya -->
>Forrest.
>So you would have to find an entry point into CVS's src/documentation/xdocs
>(wouldn't do a modifiable CVSSource here as well?
>
concerning the actual access to CVS it certainly makes sense, but I
guess one wants more than that ;-)
btw, have you been able to make CVSSource by Sylvain work on Cocoon2.1?
I tried, but it didn't work.
> I guess it would be easier
>with SVN/WebDAV :-).
>
I also see WebDAV as the future, but there are still many CVSs out there
and I am quite sure they will stay for another while ...
>
><snip/>
>
>
>
>>what do you mean by a traversable and modifiable WebDAVSource?
>>
>>
>
>A WebDAVSource object that implements the ModifiableSource and
>TraversableSource interfaces, which have been moved to the
>org.apache.excalibur.source package now.
>
>SourceWritingTransformer already operates on ModifiableSource. Additionally
>you would need a DirectoryGenerator that operates on TraversableSource
>(similar to the SourceDescriptionGenerator in Cocoon's Slide block).
>
ok
>
>
>
>>>then all you would
>>>need is a DirectoryGenerator that operates on TraversableSource and
>>>the SourceWritingTransformer to add sophisticated (and generic)
>>>editing capabilities to the sitemap (cleanly separated from
>>>publishing concerns - that's what IMHO every site administrator
>>>wants).
>>>
>>>Versioning is for free if you enable auto-versioning (something that
>>>even Subversion aims to implement) on the staging WebDAV server.
>>>
>>>
>>>
>>has SVN deltaV actually fully implemented yet?
>>
>>
>
>Not yet, but they are heading to it (IIRC what Greg Stein said at OSCOM :-)
>
>
>
>>>But a
>>>WebDAVSource could even open more possibilities by implementing
>>>VersionableSource or InspectableSource (attaching arbitrary metadata
>>>via something like a SourcePropsWritingTransformer :-).
>>>
>>>
>>>
>>I can see the power of a WebDAVSource. Do you think the WebDAV
>>implementation of Slide can be reused
>>for a WebDAVSource?
>>
>>
>
>Basically there are now 3 implementations to choose from in Slide's CVS.
>-The JSR 170 proposal which sits on top of a WebDAV transport layer IIUC.
>-The JSR 147 proposal which Software AG currently pushes to implement.
>
does SoftwareAG want to implement (http://jcp.org/en/jsr/detail?id=147)
into Slide?
>-The "old" Slide WebDAV client library which is an extension to commons-http
>and would be my first choice currently since it's the most stable.
>
you mean Side's WebDAV servlet?
Thanks
Michael
>
>Regards
>Guido
>--
>
>Guido Casper
>-------------------------------------------------
>S&N AG, Open Source Competence Center
> Tel.: +49-5251-1581-87
>Klingenderstr. 5 mailto:gcasper@s-und-n.de
>D-33100 Paderborn http://www.s-und-n.de
>-------------------------------------------------
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
>For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: [RT] Using Lenya with Forrest for ASF sites
Posted by Guido Casper <gc...@s-und-n.de>.
Michael Wechner wrote:
> Guido Casper wrote:
>
>> I don't understand how you want to use Lenya for ASF sites,
>>
>
> I think the goal would be to simplify the "updating" process
>
> http://cocoon.apache.org/lenya/community/website-update.html
>
> which basically means certain committers have the module
> "project-site" within their
> local CVS workspace. Checkin means in this sense "ready to publish"
> and
> as soon as
> sombody is updating the corresponding module on daedalus one is
> actually publishing the data.
Ah, so the wanted solution would not be Forrest --> Lenya but Lenya -->
Forrest.
So you would have to find an entry point into CVS's src/documentation/xdocs
(wouldn't do a modifiable CVSSource here as well? I guess it would be easier
with SVN/WebDAV :-).
<snip/>
> what do you mean by a traversable and modifiable WebDAVSource?
A WebDAVSource object that implements the ModifiableSource and
TraversableSource interfaces, which have been moved to the
org.apache.excalibur.source package now.
SourceWritingTransformer already operates on ModifiableSource. Additionally
you would need a DirectoryGenerator that operates on TraversableSource
(similar to the SourceDescriptionGenerator in Cocoon's Slide block).
>> then all you would
>> need is a DirectoryGenerator that operates on TraversableSource and
>> the SourceWritingTransformer to add sophisticated (and generic)
>> editing capabilities to the sitemap (cleanly separated from
>> publishing concerns - that's what IMHO every site administrator
>> wants).
>>
>> Versioning is for free if you enable auto-versioning (something that
>> even Subversion aims to implement) on the staging WebDAV server.
>>
>
> has SVN deltaV actually fully implemented yet?
Not yet, but they are heading to it (IIRC what Greg Stein said at OSCOM :-)
>
>> But a
>> WebDAVSource could even open more possibilities by implementing
>> VersionableSource or InspectableSource (attaching arbitrary metadata
>> via something like a SourcePropsWritingTransformer :-).
>>
>
> I can see the power of a WebDAVSource. Do you think the WebDAV
> implementation of Slide can be reused
> for a WebDAVSource?
Basically there are now 3 implementations to choose from in Slide's CVS.
-The JSR 170 proposal which sits on top of a WebDAV transport layer IIUC.
-The JSR 147 proposal which Software AG currently pushes to implement.
-The "old" Slide WebDAV client library which is an extension to commons-http
and would be my first choice currently since it's the most stable.
Regards
Guido
--
Guido Casper
-------------------------------------------------
S&N AG, Open Source Competence Center
Tel.: +49-5251-1581-87
Klingenderstr. 5 mailto:gcasper@s-und-n.de
D-33100 Paderborn http://www.s-und-n.de
-------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: [RT] Using Lenya with Forrest for ASF sites
Posted by Michael Wechner <mi...@apache.org>.
Guido Casper wrote:
>Nicola Ken Barozzi wrote:
><snip/>
>
>
>>Another *very* important goal, maybe even more important, is to have
>>users be able to collaborate on the docs with a better system than the
>>Wiki, that has no real workflow, and with a nice and compelling
>>editing environment.
>>
>>What we just need is to be able to handle both scenarios - the web
>>form one and the direct checking one -.
>>
>>What I now need is to understand how Forrest has to change to be able
>>to ship the Lenya "option" without the two projects having to chase
>>each other every couple of weeks.
>>
>>
>
>No change to Forrest but just have a Lenya installation release/copy content
>to a modifiable CVSSource?
>
agreed. We probably just have to create a publication which has
CVSSource implemented and point into the Forrest workspace.
Thanks
Michael
>
>
>
>>Ideas?
>>
>>
>
>Just that :-)
>
>Guido
>--
>
>Guido Casper
>-------------------------------------------------
>S&N AG, Open Source Competence Center
> Tel.: +49-5251-1581-87
>Klingenderstr. 5 mailto:gcasper@s-und-n.de
>D-33100 Paderborn http://www.s-und-n.de
>-------------------------------------------------
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
>For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: [RT] Using Lenya with Forrest for ASF sites
Posted by Guido Casper <gc...@s-und-n.de>.
Nicola Ken Barozzi wrote:
<snip/>
> Another *very* important goal, maybe even more important, is to have
> users be able to collaborate on the docs with a better system than the
> Wiki, that has no real workflow, and with a nice and compelling
> editing environment.
>
> What we just need is to be able to handle both scenarios - the web
> form one and the direct checking one -.
>
> What I now need is to understand how Forrest has to change to be able
> to ship the Lenya "option" without the two projects having to chase
> each other every couple of weeks.
No change to Forrest but just have a Lenya installation release/copy content
to a modifiable CVSSource?
>
> Ideas?
Just that :-)
Guido
--
Guido Casper
-------------------------------------------------
S&N AG, Open Source Competence Center
Tel.: +49-5251-1581-87
Klingenderstr. 5 mailto:gcasper@s-und-n.de
D-33100 Paderborn http://www.s-und-n.de
-------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: [RT] Using Lenya with Forrest for ASF sites
Posted by Andreas Hartmann <an...@apache.org>.
Nicola Ken Barozzi wrote:
> What I now need is to understand how Forrest has to change to be able to
> ship the Lenya "option" without the two projects having to chase each
> other every couple of weeks.
I started a thread about a Forrest publication template a while ago,
but at this time there wasn't much interest. The gmane search seems
to be broken, so I can't send you the thread link.
Unfortunately, dynamic publication templates are not yet supported.
This means that everytime Forrest changes, the publication has to be
updated. But if the intersection of Forrest files and publication
files is empty, this would be no problem.
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: [RT] Using Lenya with Forrest for ASF sites
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Michael Wechner wrote, On 30/06/2003 0.49:
> Guido Casper wrote:
>
>> I don't understand how you want to use Lenya for ASF sites,
>
> I think the goal would be to simplify the "updating" process
>
> http://cocoon.apache.org/lenya/community/website-update.html
>
> which basically means certain committers have the module "project-site"
> within their
> local CVS workspace. Checkin means in this sense "ready to publish" and
> as soon as
> sombody is updating the corresponding module on daedalus one is actually
> publishing the data.
Or checkins mean "added a version to check-merge into the stable page".
Another *very* important goal, maybe even more important, is to have
users be able to collaborate on the docs with a better system than the
Wiki, that has no real workflow, and with a nice and compelling editing
environment.
What we just need is to be able to handle both scenarios - the web form
one and the direct checking one -.
What I now need is to understand how Forrest has to change to be able to
ship the Lenya "option" without the two projects having to chase each
other every couple of weeks.
Ideas?
> So instead of using the command line you could use Lenya as interface,
> which would help to simplify
> certain things and circumvent certain mistakes. The meaning of "help"
> certainly depends on the "editor's" mindset ;-)
:-))
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: [RT] Using Lenya with Forrest for ASF sites
Posted by Michael Wechner <mi...@apache.org>.
Guido Casper wrote:
>I don't understand how you want to use Lenya for ASF sites,
>
I think the goal would be to simplify the "updating" process
http://cocoon.apache.org/lenya/community/website-update.html
which basically means certain committers have the module "project-site"
within their
local CVS workspace. Checkin means in this sense "ready to publish" and
as soon as
sombody is updating the corresponding module on daedalus one is actually
publishing the data.
So instead of using the command line you could use Lenya as interface,
which would help to simplify
certain things and circumvent certain mistakes. The meaning of "help"
certainly depends on the "editor's" mindset ;-)
> but FWIW
>here are my opinions on the matter of integrating Lenya with Forrest.
>
>According to
>http://cocoon.apache.org/lenya/project/roadmap.html
>Lenya aims to integrate Slide as a content repository.
>
well, as data abstraction layer (maybe JSR-170 at a certain point of
time) and WebDAV implementation
>
>While I would have mixed feelings about Lenya coupling itself that tightly
>to Slide (by using Slide's low level Java API) I would love to see Lenya
>building its repository on the Source interfaces (similar to what's in
>Cocoon's Slide block). That way Slide could easily be swapped with another
>WebDAV server (once a WebDAVSource is available :-) or CVS for that matter.
>
agreed, it should definitely be replaceable. That's why I think WebDAV
and something like JSR-170
are so important (or also the servlet API). But actually it would also
be nice for Cocoon itself ;-)
>
>Releasing content would mean not much more than copying content from the
>staging WebDAV server to a live WebDAV server which could be a
>non-versioning server like mod_dav
>
right, but it would need triggers to notify whatever service.
Also workflow needs to be considered, even if it's very simple like in
most cases.
> (which BTW is magnitudes faster than
>Slide ever will be). Not difficult to imagine how you get a very flexible
>and scalable architecture by just adding more publishing Cocoon instances.
>
>To integrate Forrest you just would have to add a WebDAV deployment target
>to Forrest (forrestbot currently only deals with static site generation
>AFAIU) that copies the resources to a WebDAVServer and adjusts the sitemap's
>"src" attributes to use the DAV protocol or HTTP for that matter. You could
>even copy the sitemap on the WebDAV server as well, since you could mount
>the sitemap via DAV protocol.
>
>If you have a traversable and modifiable WebDAVSource
>
what do you mean by a traversable and modifiable WebDAVSource?
> then all you would
>need is a DirectoryGenerator that operates on TraversableSource and the
>SourceWritingTransformer to add sophisticated (and generic) editing
>capabilities to the sitemap (cleanly separated from publishing concerns -
>that's what IMHO every site administrator wants).
>
>Versioning is for free if you enable auto-versioning (something that even
>Subversion aims to implement) on the staging WebDAV server.
>
has SVN deltaV actually fully implemented yet?
> But a
>WebDAVSource could even open more possibilities by implementing
>VersionableSource or InspectableSource (attaching arbitrary metadata via
>something like a SourcePropsWritingTransformer :-).
>
I can see the power of a WebDAVSource. Do you think the WebDAV
implementation of Slide can be reused
for a WebDAVSource?
Thanks
Michael
>
>My 2 cents
>
>Guido
>--
>Guido Casper
>-------------------------------------------------
>S&N AG, Open Source Competence Center
> Tel.: +49-5251-1581-87
>Klingenderstr. 5 mailto:gcasper@s-und-n.de
>D-33100 Paderborn http://www.s-und-n.de
>-------------------------------------------------
>
>Nicola Ken Barozzi wrote:
>
>
>>Hi guys! I'm starting a RT==RandomThought about using Lenya with
>>Forrest.
>>
>> Scenario
>>----------
>>
>>Any OS product must recieve good beta testing. It's an integral part
>>of it, and closes the feedback loop.
>>
>>The Apache Software Foundation Projects are an excellent testbed,
>>because:
>>
>> 1 - high load
>> 2 - many users
>> 3 - very good admins
>> 4 - many users are advanced developers
>>
>>The Apache HTTPD server is used to drive the ASF website, and this
>>makes it a good showcase and also a good mean of testing it.
>>
>>Apache James wants to be the ASF mail server.
>>Cocoon would love to become the webapp server for publishing.
>>Forrest was in fact initially an implememtation based on Cocoon to
>>make the website for Apache and other OS projects.
>>
>>Lenya? Well, conceptually Lenya fits in very well in this scenario, as
>>it adds CMS capability to Cocoon, which is what we still need in our
>>infrastructure.
>>
>> Needs
>>-------
>>
>>What are the needs AFAIK that Lenya has to fulfill?
>>Well, it has to make it possible to edit pages using the browser, and
>>add publishing workflow to the picture. But ok, this is standard.
>>
>>What I don't have a precise idea on how to do it is integration with
>>CVS and with Forrest. Users must be able to generate the site using
>>Forrest locally, and also change the site locally and synch with CVS
>>as they do now. AFAIK though this breaks the workflow...
>>
>>Wait, but we need not stick to CVS, as SVN can also be used.
>>SubVersion is WebDav enabled, if this can help you.
>>
>>In practice, what would you guys suggest doing for integrating Lenya
>>in Forrest and making it all work with CVS or SVN?
>>
>>I want to install Lenya+Forrest combo on a Server, configure it to
>>use a repository, and have changes come in both via SVN or the web
>>interface.
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
>For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: [RT] Using Lenya with Forrest for ASF sites
Posted by Guido Casper <gc...@s-und-n.de>.
I don't understand how you want to use Lenya for ASF sites, but FWIW
here are my opinions on the matter of integrating Lenya with Forrest.
According to
http://cocoon.apache.org/lenya/project/roadmap.html
Lenya aims to integrate Slide as a content repository.
While I would have mixed feelings about Lenya coupling itself that tightly
to Slide (by using Slide's low level Java API) I would love to see Lenya
building its repository on the Source interfaces (similar to what's in
Cocoon's Slide block). That way Slide could easily be swapped with another
WebDAV server (once a WebDAVSource is available :-) or CVS for that matter.
Releasing content would mean not much more than copying content from the
staging WebDAV server to a live WebDAV server which could be a
non-versioning server like mod_dav (which BTW is magnitudes faster than
Slide ever will be). Not difficult to imagine how you get a very flexible
and scalable architecture by just adding more publishing Cocoon instances.
To integrate Forrest you just would have to add a WebDAV deployment target
to Forrest (forrestbot currently only deals with static site generation
AFAIU) that copies the resources to a WebDAVServer and adjusts the sitemap's
"src" attributes to use the DAV protocol or HTTP for that matter. You could
even copy the sitemap on the WebDAV server as well, since you could mount
the sitemap via DAV protocol.
If you have a traversable and modifiable WebDAVSource then all you would
need is a DirectoryGenerator that operates on TraversableSource and the
SourceWritingTransformer to add sophisticated (and generic) editing
capabilities to the sitemap (cleanly separated from publishing concerns -
that's what IMHO every site administrator wants).
Versioning is for free if you enable auto-versioning (something that even
Subversion aims to implement) on the staging WebDAV server. But a
WebDAVSource could even open more possibilities by implementing
VersionableSource or InspectableSource (attaching arbitrary metadata via
something like a SourcePropsWritingTransformer :-).
My 2 cents
Guido
--
Guido Casper
-------------------------------------------------
S&N AG, Open Source Competence Center
Tel.: +49-5251-1581-87
Klingenderstr. 5 mailto:gcasper@s-und-n.de
D-33100 Paderborn http://www.s-und-n.de
-------------------------------------------------
Nicola Ken Barozzi wrote:
> Hi guys! I'm starting a RT==RandomThought about using Lenya with
> Forrest.
>
> Scenario
> ----------
>
> Any OS product must recieve good beta testing. It's an integral part
> of it, and closes the feedback loop.
>
> The Apache Software Foundation Projects are an excellent testbed,
> because:
>
> 1 - high load
> 2 - many users
> 3 - very good admins
> 4 - many users are advanced developers
>
> The Apache HTTPD server is used to drive the ASF website, and this
> makes it a good showcase and also a good mean of testing it.
>
> Apache James wants to be the ASF mail server.
> Cocoon would love to become the webapp server for publishing.
> Forrest was in fact initially an implememtation based on Cocoon to
> make the website for Apache and other OS projects.
>
> Lenya? Well, conceptually Lenya fits in very well in this scenario, as
> it adds CMS capability to Cocoon, which is what we still need in our
> infrastructure.
>
> Needs
> -------
>
> What are the needs AFAIK that Lenya has to fulfill?
> Well, it has to make it possible to edit pages using the browser, and
> add publishing workflow to the picture. But ok, this is standard.
>
> What I don't have a precise idea on how to do it is integration with
> CVS and with Forrest. Users must be able to generate the site using
> Forrest locally, and also change the site locally and synch with CVS
> as they do now. AFAIK though this breaks the workflow...
>
> Wait, but we need not stick to CVS, as SVN can also be used.
> SubVersion is WebDav enabled, if this can help you.
>
> In practice, what would you guys suggest doing for integrating Lenya
> in Forrest and making it all work with CVS or SVN?
>
> I want to install Lenya+Forrest combo on a Server, configure it to
> use a repository, and have changes come in both via SVN or the web
> interface.
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org