David Sean Taylor wrote:
Carsten
OK, just means we have to copy the generated docs into a portals/site
directory and check in from there. Seems easy enough
+1
More or less. We check in the generated site to a particular spot in
the svn repository (e.g. https://svn.apache.org/repos/asf/portals/www)
and then log on to people.apache.org and cd to /www/portals.apache.org
and do a svn update which will copy the changed files from the svn
repository to the /www directory. So the /www/portals.apache.org IS a
svn checkout of https://svn.apache.org/repos/asf/portals/www.
This way, it's very easy to restore the website, which is important to
infrastructure folks and easy for us to publish. Once files are copied
into /www/portals.apache.org, they automagically get replicated to the
live website.
I'm suggesting we use ...repos/asf/portals/www because
...repos/asf/portals/site already contains the source for the portals
site itself. Each project retains its own way of storing its site
source files and generating them.
--
Julie MacNaught
IBM Research
[EMAIL PROTECTED]
[EMAIL PROTECTED]
DADB E3B5 8CB7 6B9B F4A0 8BF7 E830 1848 16A8 D3AB
