octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Website update


From: Mike Miller
Subject: Re: Website update
Date: Wed, 6 Jul 2016 10:07:34 -0700
User-agent: Mutt/1.6.0 (2016-04-01)

On Wed, Jul 06, 2016 at 16:28:15 +0000, Alex Krolick wrote:
> The site is built in Jekyll and generates static files. It could be easily
> copied from Git to a Hg repository. I think this was previously discussed
> and turned down in favor of hosting on GNU infrastructure, but it is
> possible to use a custom domain on Github pages
> <https://help.github.com/articles/using-a-custom-domain-with-github-pages/>.

I'm familiar with Jekyll and static site generation and GitHub pages and
all that.

I like Jekyll and I believe it may be an appropriate tool for generating
the Octave project web site. Hosting on GitHub is not (but fine for your
personal testing purposes).

If we continue to host the project web site on www.gnu.org (which I
think may not be absolutely *required*, but is encouraged and
preferred), then the site must continue to be deployed via "cvs commit"
to the /web/octave CVS repository on Savannah.

The obvious conclusion is that there will be two repositories for the
web site, one for maintaining the text source files and images,
preferably in a Mercurial repository hosted on hg.octave.org, and the
CVS repository for deploying the site after it has been generated.

I'm imagining some kind of "make deploy" target that runs jekyll, copies
the generated site into the CVS project directory, and does a cvs commit
with a generated commit message based on the hg id of the source repo.

-- 
mike



reply via email to

[Prev in Thread] Current Thread [Next in Thread]