lucene-java-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucene-java Wiki] Update of "HowToUpdateTheWebsite" by OtisGospodnetic
Date Fri, 13 Mar 2009 17:32:11 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-java Wiki" for change notification.

The following page has been changed by OtisGospodnetic:
http://wiki.apache.org/lucene-java/HowToUpdateTheWebsite

The comment on the change is:
Attempt to make instructions more specific and easier to follow.  Includes Qs.

------------------------------------------------------------------------------
  
     1. Install [http://forrest.apache.org/ Apache Forrest] version 0.8
     1. Checkout the content (see above for the subversion url to use).
-    1. Change the root forrest directory.  For the versioned site, this is lucene/src/site;
for the unversioned site, it's main directory you just checked out.
+      1. svn co https://svn.apache.org/repos/asf/lucene/java/site site-unversioned
+      1. svn co https://svn.apache.org/repos/asf/lucene/java/trunk/src/site site-versioned
+    1. Change the root forrest directory to one of the checked out directories.  For the
versioned site, this is lucene/src/site (OG: where does "lucene" come from?  Is this specific
to how one checks things out of svn?); for the unversioned site, it's main directory you just
checked out (OG: main being "site-unversioned" ?).
+      1. cd site-unversioned
+      1. cd site-versioned
-    1. Make your desired website changes to the source files in the subdirectory src/documentation.
+    1. Make your desired website changes to the source files in the subdirectory src/documentation
(OG: in both checkouts?)
     1. Optionally, run "forrest run" and browse to http://localhost:8888 to review the changes
and iterate.  You should be able to modify the source documents and hit reload on your browser
to see the changes.
-    1. When you are satisfied with your changes, stop the forrest server and then regenerate
the site with forrest by running "forrest site".  Then, recursively copy build/site/* to ../../docs/*
(for the versioned site) and docs/* (for the unversioned site), and commit changes to both
src/documentation and docs (add any new files first, but exclude the build directory).
+    1. When you are satisfied with your changes, stop the forrest server and then regenerate
the site with forrest by running "forrest site".  Then, recursively copy site-versioned/build/site/*
to ../../docs/* (for the versioned site) (OG: is ../../docs/ specific to some specific way
of checking out of svn? e.g. this doesn't work with exaple svn co commands above) and docs/*
(for the unversioned site), and commit changes to both src/documentation and docs (add any
new files first, but exclude the build directory).
     1. The site will automatically be exported from svn to people.apache.org by a script
running in Grant's crontab on p.a.o., and then Apache's main web servers will reflect the
change within an hour according to the process described at http://www.apache.org/dev/project-site.html).
 Grant's cron job currently (as of 1/22/2009) looks like this:
  {{{
  03 6 * * * <OMITTED>/bin/exportLuceneDocs.sh > /tmp/lucene-nightly.log 2>&1

Mime
View raw message