[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [qemu-web PATCH] Import historical documentation
|
From: |
Michael Roth |
|
Subject: |
Re: [Qemu-devel] [qemu-web PATCH] Import historical documentation |
|
Date: |
Fri, 07 Dec 2018 09:59:20 -0600 |
|
User-agent: |
alot/0.7 |
Quoting Daniel P. Berrangé (2018-12-07 03:44:45)
> 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.
I have scripts to generate/build/test tarballs, but do the uploads manually
and then manually do the qemu-web.git commit. So whether it's an extra upload
or and extra commit/commit step works just as well on my end.
Uploading the docs alongs with the tarballs at the appropriate locations
and having jekyll do any additional processing as part of the
_data/releases.yml update/commit would probably be ideal for me, but any of
these approaches should work fine for me. Hidden directory makes sense if we
don't plan to use them directly so we can easily delete them afterward
to save space.
>
> 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 :|
>