humphd / humphd/next

Create a GitHub Release to store our VM binary files

Open
#92 2 comments 0 reactions 0 assignees View on GitHub
automation terminal
Dominant language
JavaScript
Stars
14
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Once we land #83, we're going to have a set of binary files we need to download/deploy every time we build the site on Travis, including:

* [seabios.bin](https://github.com/copy/v86/blob/master/bios/seabios.bin?raw=true)
* [vgabios.bin](https://github.com/copy/v86/blob/master/bios/vgabios.bin?raw=true)
* and our new `v86-linux.iso` that buildroot creates.

The GitHub docs suggesting [creating a Release](https://help.github.com/articles/creating-releases/) when you have binary files like this. I also notice that [Travis can auto-deploy GitHub Releases](https://docs.travis-ci.com/user/deployment/releases/).

So we should figure out how to do this properly. Can we somehow automate this? Or do we need to manually create a release every time we update the VM binary files (I don't think it will be often)? We could also consider moving the buildroot stuff, Docker stuff, and binary files to a new repo that only does this.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.