On Thu, Nov 18, 2010 at 12:50 AM, Fernando Perez <fperez....@gmail.com> wrote: > On Wed, Nov 17, 2010 at 2:33 AM, Dag Sverre Seljebotn > <da...@student.matnat.uio.no> wrote: >> >> - Static web site content (you just create a repository which it >> serves as static content, e.g, http://cournape.github.com/Bento/) > > If you go down the github route, I'd suggest a slightly different > alternative than github's default for the creation of static content. > Their approach uses a hidden DAG in the repo called gh-pages, which > eternally pollutes your repo with all static html you generate. It's > easy with a tiny bit of scripting to create instead the gh-pages > content in a *separate repo* completely decoupled from the main one. > That's what we do here: > > https://github.com/fperez/datarray # main repo > http://fperez.github.com/datarray-doc/ # gh-pages in separate repo. > > The tool that does the job is this trivial script: > > https://github.com/fperez/datarray/blob/master/doc/gh-pages.py > > I'll be happy to provide pointers if you want them. > > I just wanted to let you know so that you avoid what I think is a > poor, but easy to work around, design choice of github's pages > implementation.
Two improvements over your setup: * you can have your own domain point to the pages (e.g. docs.sympy.org are hosted at github servers) * you can set the "gh-pages" as the default (and only) branch in the datarray-doc, just like this: https://github.com/sympy/sympy_doc, and then this little issue becomes a non-issue, because you just pull and push into the repo and don't worry about anything (there is no master branch, just the gh-pages branch, and as a result, you just do "git pull, git push origin") Ondrej _______________________________________________ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
