Quoting Robin Green <greenrd@hotmail.com>:
> Giacomo Pati <giacomo@apache.org> wrote:
> >For this I
> >need to change the xdocs/site-docs.xml in the C1 repository to have a
> link
> >into
> >this subdir. Robin, is this ok for you?
>
> Go ahead.
>
> >Do you have any conventions we still
> >need to do concerning to update the Cocoon site?
>
> I usually only update the website when releases occur, but I have no
> problem
> with more frequent updates.
>
> I guess you probably know all this already,
Well, I've never done it 'til now.
> but I just do
>
> build.sh -verbose site
> cvs commit foo (if not already done)
> cd ../xml-site/cocoon
> tar cvfz ../cocoon.tgz *
> scp ../cocoon.tgz greenrd@apache.org:/tmp
> ssh greenrd@apache.org
> cd /www/xml.apache.org/cocoon
> tar xvfz /tmp/cocoon.tgz
> rm -f /tmp/cocoon.tgz
I might do it on locus directly.
> more or less as Stefano recommended. There is a CVS tree there but no
> point
> in using it - only source xdocs need to be version controlled.
> But - IMPORTANT - remember to do
>
> cd /www/xml.apache.org/cocoon
> chmod -R g+w *
Ok, thanks pointing me to it.
> (not a+w) on apache.org after uploading, otherwise other commiters might
> get
> permission denied errors when they update the site. Or you could try scp
> -p
> but that didn't work for me.
Thanks,
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
|