[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [qemu-web PATCH] Import historical documentation
|
From: |
Daniel P . Berrangé |
|
Subject: |
Re: [Qemu-devel] [qemu-web PATCH] Import historical documentation |
|
Date: |
Fri, 7 Dec 2018 09:44:45 +0000 |
|
User-agent: |
Mutt/1.10.1 (2018-07-13) |
On Thu, Dec 06, 2018 at 09:01:46PM +0100, Paolo Bonzini wrote:
> On 04/12/18 11:56, Thomas Huth wrote:
> > I think it would be best if we find a way to automate this process, e.g.
> > when a new release is tagged, a script generates the docs and puts them
> > somewhere on the web server, into the right new folder based on the name
> > of the tag. However, I don't know the qemu server well enough to know
> > whether that's possible or not ... maybe Jeff or Paolo can comment on
> > this...
>
> There are two possibilities: putting the docs on download.qemu.org and
> going for Marc-André's styling solution, or using a dash of sed to
> remove the <head> and use Jekyll to generate the page.
I would really like the docs to be properly integrated into the web
site including navbar / footers, not just using a similar-ish styling.
> Either way, there isn't much to do on the webserver side, so a better
> person to ask would be Mike Roth as he's the Guy Who Does The Releases.
> For either solution he'd have to build the documentation and scp it (if
> we go for download.qemu.org) or commit it to qemu-web.git (if we go for
> Jekyll). I guess he has scripts already to automate part of the release
> process, but I have no idea if the website update is automated already.
A third option is to scp the docs to download.qemu.org (perhaps in a hidden
dir), and then have a jekyll plugin that pulls that in & applies the
template.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|