mahout-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache Mahout > How To Update The Website
Date Sun, 27 Jun 2010 17:28:00 GMT
Space: Apache Mahout (
Page: How To Update The Website (

Edited by Robin Anil:
h2. Some Do's and Dont's of updating the wiki
# Keep the wiki cleanly formatted. Assume the title is of size h1
# Try to keep a single page for a topic instead of starting multiple one. If the topics are
related, put it under as a child under the similar page.
# Notify the developers of orphaned or broken links.
# Use the page title to link pages so that they get correctly updated by when someone changes
the title
Correct format
[Name of the link|How To Update The Website]

The following is incorrect. Please change then when you encounter them
[Name of the link|http://<path to>/how to update the website.html]

To update the pages, update the wiki directly. Do not change the title of top level pages
without updating the same on the landing page.

h2. How to update the mahout home page
(*NOTE:* _You need committer rights to modify the home page._)
To update the home page
# Commit changes to the website landing page at
# Ensure all outgoing links from the landing page to the wiki are working
# The site will automatically be exported from svn by a script running in 
Grant's crontab on p.a.o on a nightly basis:
        04 4 * * * /home/gsingers/bin/ > /home/gsingers/bin/mahout.log
It takes about 48 hours for the links to propagate. Once the links are updated, change title
on the wiki.

*NOTE:* The following is deprecated

# Install [Apache Forrest|] version 0.8. Make sure you have write
permissions on the directory where Apache Forrest is installed, the first time your run Forrest
it will attempt to create a plug-ins directory and download several plug-ins.  Forrest does
not work w/ JDK 1.6.  This is particularly onerous on a Mac, since Apple seems to think Java
1.5 is the same as Java 1.6.  To fix, see
# Checkout the Mahout site code [].
# Change directory to where it was checked out
# Run forrest to build current version of documentation to make sure that Forrest was correctly
installed. The generated site will be in ./build/site/.
# Make your desired website changes to the source files in ./src/ and regenerate the site
with forrest.
# Run "forrest run" and browse to http://localhost:8888 to review the changes. You should
be able to modify the source documents and hit reload on your browser without rebuilding the
# When you are satisfied with your changes, regenerate the site with forrest by running "forrest
# *(recursively) copy ./build/site/\* to ./publish, and commit changes to both ./src and ./publish
(add any new files first, but exclude the build directory).  This step is very important,
if you miss it, your changes will not appear on the site after the next step.*
# The site will automatically be exported from svn by a script running in Grant's crontab
on p.a.o on a nightly basis:
        04 4 * * * /home/gsingers/bin/ > /home/gsingers/bin/mahout.log

Change your notification preferences:

View raw message