Hi, ASF Infra is experimenting with a (much) faster way [1] of replicating website content to the ASF's live websites, provided said content is committed to SVN. They're looking for volunteer projects to test that (aka guinea pigs ;-)
Currently, the part of our website that's generated from Confluence [2] is not committed to SVN, but rather goes directly to the website, as described in appendix below. I suggest changing the process slightly, to update content coming from SLINGxSITE the scenario would be: 1. Edit in Confluence 2. Wait for auto export, or trigger it 3. cd <my sling svn sandbox>/site/site (new folder at [3]) 3. rsync -rcv [email protected]:/www/confluence-exports/SLINGxSITE . 4. review and commit 5. SvnWcSub/SvnPubSub picks up changes syncs to live site (typically within a minute) At step 5 we could also setup a staging site easily, using an SVN branch, if we want. The advantages would be better overview of what's in the site and how things are generated, along with much faster updates of the live site - whoever edits the docs can immediately check that they're online. This would also allow us to play more with generated content, like for example creating tag-based navigation pages by running a script or app on the content before step 4. And maybe also easily include individual bundle's documentations (generated with mvn site/APT?) under paths like /bundles/somebundle/V1.2.34 to have per-bundle versioned docs. Last but not least, we'd have all the history of our website content in SVN. The only downside is a slightly more "manual" update process, as described above, but that's not too painful IMHO, and we can create a script for that if needed. What do people think? -Bertrand [1] http://mail-archives.apache.org/mod_mbox/www-infrastructure-dev/200909.mbox/%[email protected]%3e [2] http://cwiki.apache.org/confluence/display/SLINGxSITE/Apache+Sling [3] http://svn.apache.org/repos/asf/sling/site/ Current sling.apache.org update process: 1. Confluence auto-export writes to /www/confluence-exports/SLINGxSITE on people.apache.org. This happens quickly, within 1-2 minutes usually. 2. A command from user fmeschbe's crontab copies that to /www/sling.apache.org/site 3. An ASF script rsyncs that (every few hours IIRC) to the live website
