to stuff your own little projects, (assuming you're in unix)
it's super convenient to add this to the cocoon sitemap:
<map:pipeline>
<map:match pattern="~*/**">
<map:mount check-reload="yes" src="/home/{1}/public_html/" uri-prefix="~{1}"/>
<!--
This is an example of using a sitemap variable: "{1}" Curly
brackets denote sitemap variables, here the one named "1".
-->
</map:match>
<map:match pattern="~*">
<map:redirect-to uri="{0}/"/>
</map:match>
</map:pipeline>
then stick whatever kindof automounting sitemap you want in your
public_html directory.
the greatest benefit of this, is if everyone on your shared system sets up
their vm this way, you can test stuff on someone else's if yours is acting
strange or you have patched it one way or another.
Tim
On Fri, Jul 05, 2002 at 11:50:20AM -0400, Jason Foster wrote:
> > But we have already the global mount:
> >
> > <!-- mount everything else -->
> > <map:match pattern="*/**">
> > <map:mount check-reload="yes" src="{1}/" uri-prefix="{1}"/>
> > </map:match>
> >
> > I think this is enough.
>
> If you're willing to add more directories to the contents of ".../webapps/
> cocoon", then sure. However it then get trickier to determine what is
> yours and what came with cocoon. I use the "mount" directory as a place to
> hold the little projects I am working on and it has been pretty convenient.
>
> Making everything work in "mount" is as simple as putting a stub sitemap in
> ".../webapps/cocoon/mount" that does the same "global mount" match that is
> done at the base sitemap level.
>
> Jason Foster
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
