search

redcode-labs / RedNixOS

NixOS-based 'distro' for cybersecurity enthusiasts
ISC License
182 stars 9 forks source link

[enhancement] provide pre-built .iso for release #8

Open unrooted opened 2 years ago

unrooted commented 2 years ago

as the name suggests

AkechiShiro commented 2 years ago

I would be interested in this feature, and I could maybe provide some help, but I don't know how to build such an .iso file

unrooted commented 2 years ago

@AkechiShiro thanks for your interest. It's actually quite easy. you have to grab alpha release and run nix build within the extracted folder, it will produce the .iso file which you can easily use as regular Linux .iso file.

The only thing is - GitHub is limiting the size of release files (if I remember correctly, it's 1Gb) and RedNixOS v0.1-alpha .iso file is over 6Gb (!). Hence, we need to have a place to store the pre-built .iso files for each release.

I've thought about using RuTracker or setting up a proper torrent box, since the file is quite big, the torrent way of distribution sounds great. If not this, SourceForge also sounds promising, but I haven't looked much into this solution.

All kind of suggestions/help is welcome.

AkechiShiro commented 2 years ago

I suggest using either Git-LFS for that and also for the storage server I'm not sure if Git-LFS can handle it too

AkechiShiro commented 2 years ago

Also so release could be automatically rolled out with CI/CD no ? Using Github Actions

AkechiShiro commented 2 years ago

@AkechiShiro thanks for your interest. It's actually quite easy. you have to grab alpha release and run nix build within the extracted folder, it will produce the .iso file which you can easily use as regular Linux .iso file.

The only thing is - GitHub is limiting the size of release files (if I remember correctly, it's 1Gb) and RedNixOS v0.1-alpha .iso file is over 6Gb (!). Hence, we need to have a place to store the pre-built .iso files for each release.

I've thought about using RuTracker or setting up a proper torrent box, since the file is quite big, the torrent way of distribution sounds great. If not this, SourceForge also sounds promising, but I haven't looked much into this solution.

All kind of suggestions/help is welcome.

This should be thoroughly documented in the repo also.

unrooted commented 2 years ago

Actually this is documented in project's wiki, sorry if that wasn't clear.

Git-LFS - I dunno if it will handle that yeah we can automatically do CI/CD with GH actions as well, but that again should push it to some kind of remote where releases would be stored