Create a Private Repository

When creating custom AstLinux images, you can setup a private repository to maintain custom builds after you created an initial image with ./scripts/astlinux-makeimage.

On a public or private HTTPS server, create a file structure similar to:

custom-firmware-1.x/
custom-firmware-1.x/genx86_64-serial
custom-firmware-1.x/genx86_64-serial/astlinux-1.5-6096-5c954d.tar.gz
custom-firmware-1.x/genx86_64-serial/astlinux-1.5-6096-5c954d.tar.gz.sha1
custom-firmware-1.x/genx86_64-serial/ver
custom-firmware-1.x/genx86_64-vm
custom-firmware-1.x/genx86_64-vm/astlinux-1.5-6074-c9d0c1.tar.gz
custom-firmware-1.x/genx86_64-vm/astlinux-1.5-6074-c9d0c1.tar.gz.sha1
custom-firmware-1.x/genx86_64-vm/ver
custom-firmware-1.x/genx86_64
custom-firmware-1.x/genx86_64/astlinux-1.5-6075-ca0390.tar.gz
custom-firmware-1.x/genx86_64/astlinux-1.5-6075-ca0390.tar.gz.sha1
custom-firmware-1.x/genx86_64/ver

The genx86_64-serial/ver file contents is astlinux-1.5-6096-5c954d and respectively for the other “ver” files. The “.tar.gz” and “.tar.gz.sha1” files are generated in your working directory after a successful ./scripts/build. A directory must exist for each 'board' type you want to maintain.

In the AstLinux web interface Prefs Tab, define the “Repository URL:” as:

https://bla-bla.tld/custom-firmware-1.x

then use the System Tab to upgrade.

Or from the CLI…

  upgrade-run-image check https://bla-bla.tld/custom-firmware-1.x
  
  upgrade-run-image upgrade https://bla-bla.tld/custom-firmware-1.x

You can manage as many repos as you wish. For example:

https://bla-bla.tld/beta-firmware-1.x

might be used for pre-production images.

Tip -> Alternatively, s3fs can be used to mount S3 object storage used as an S3 bucket firmware repository