Re: Adds a site search to website and improves doc search(issue4894053)

[Graham Percival]

On Thu, Aug 25, 2011 at 03:19:50PM +0100, Phil Holmes wrote:
> ----- Original Message ----- From: "Graham Percival"
> <address@hidden>
> >In the short-term, I think it would be extremely helpful if you
> >could create the $HOME/lilypond/media stuff, then create the
> >website from a blank build tree -- convince yourself that you
> >can/will get the full website without running make or make doc.
> 
> I don't follow the bit about lilypond/media and I've read the CG
> about building the website a number of times.  Could you a)
> enlighten me a bit more

Hopefully?

I'm not certain what you've read, or what you've tried.  I'll
extract parts from:
http://lilypond.org/doc/v2.15/Documentation/contributor/uploading-and-security
but I'll omit anything that isn't strictly relevant in your case,
and rephrase a few other parts.  Please tell me at which stage
things become unclear.

I wasn't expecting you to be able to put this together without
asking questions (since it's taken even me a while to put stuff
together), but more specific questions about be good.


%%% Initial setup
1. create directories:
  $HOME/lilypond/
  $HOME/lilypond/media/
  $HOME/lilypond/trusted-scripts/

% To reduce the CPU burden on the shared host (as well as some
% security concerns), the ‘Documentation/pictures/’ and
% ‘Documentation/web/ly-examples/’ directories are **not**
% compiled.  We will do this ourselves right now.
2. go to your lilypond build directory.  make doc.

3. I'm going to use these variables:
  PICS=$BUILD_DIR/Documentation/pictures/out-www/
  EXAMPLES=$BUILD_DIR/Documentation/web/ly-examples/out-www/
you can either define them explicitly in bash with export, or do
it manually with copy&paste.  You'll only do this once.

  cp $PICS $HOME/lilypond/media/pictures
  cp $EXAMPLES $HOME/lilypond/media/ly-examples

4. get scripts you need.  Define these variables:
GIT=$HOME/lilypond-git
DEST=$HOME/lilypond/trusted-scripts
cp $GIT/make/website.make $DEST/website.make
cp $GIT/Documentation/lilypond-texi2html.init $DEST/lilypond-texi2html.init
cp $GIT/scripts/build/extract_texi_filenames.py $DEST/extract_texi_filenames.py
cp $GIT/scripts/build/create-version-itexi.py
$DEST/create-version-itexi.py
cp $GIT/scripts/build/create-weblinks-itexi.py
$DEST/create-weblinks-itexi.py
cp $GIT/scripts/build/mass-link.py $DEST/mass-link.py
cp $GIT/scripts/build/website_post.py $DEST/website_post.py
cp $GIT/scripts/build/bib2texi.py $DEST/bib2texi.py
cp $GIT/Documentation/web/server/lilypond.org.htaccess
$DEST/lilypond.org.htaccess
cp $GIT/Documentation/web/server/website-dir.htaccess
$DEST/website-dir.htaccess

(every "cp" should be the beginning of a new line; it's followed
by two filenames.  The lines will probably be cut in email)


5. delete your build directory.  (you don't actually need to do
this, I'm just emphasizing the magic trick.  Or maybe just rename
your build directory to build-old, or go to a different directory
called magic-website)

6. run
  make -f ../make/website.make WEBSITE_ONLY_BUILD=1 \
    TOP_SRC_DIR=$HOME/src/lilypond/ \
    TEXI2HTML_PROGRAM=texi2html \
    website
% note that this would be much easier if anybody had been
% interested in 
%   http://code.google.com/p/lilypond/issues/detail?id=1236


Note that there's a **ton** of things that could be done to make
this process easier.  The git repo is an obvious one, but there's
also a lot of robustifying that could be done in website.make.
And, of course, simply documenting this.

Cheers,
- Graham