Use github assets for releasing binary files

[Gilou]

Hi,

This is more an idea rather than a real feature request, but I see the installer gets its binary from fogproject.org, which is nice, but probably could be spared easily the bandwidth hogging by releasing and using github’s assets and redirecting/linking to them.

This can also be included in a deployment script as you can use their API, or you can upload them manually along with the release creation: https://help.github.com/articles/creating-releases/

As I couldn’t identify an obvious build script or Makefile for the binaries, I was stuck with https://wiki.fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel and https://wiki.fogproject.org/wiki/index.php/Build_FOG_file_system_with_BuildRoot to rebuild the kernel & the init.xz, are there more precise pointers to do that?
Not sure about the client part, but I haven’t even looked at that part.

Cheers
Gilles

[Gilou]

You’d end up with something like this: https://github.com/gilou/fogproject/releases/tag/1.4.0-RC-2
and github “guarantees” the link to remain as is with its tags (or release name), and gives you a /releases/latest as stated in here: https://help.github.com/articles/linking-to-releases/

[Wayne Workman]

@Gilou said in Use github assets for releasing binary files:

As I couldn’t identify an obvious build script or Makefile for the binaries, I was stuck with https://wiki.fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel and https://wiki.fogproject.org/wiki/index.php/Build_FOG_file_system_with_BuildRoot to rebuild the kernel & the init.xz, are there more precise pointers to do that?

Yes - Tom would need to share the scripts he’s wrote for doing these things.

Not sure about the client part, but I haven’t even looked at that part.

There is a powershell script in the repo that builds the client - there is also a text file explaining what is needed.