====== 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 HTTP server, create a file structure similar to:

    beta-firmware-1.x/
    beta-firmware-1.x/net5501
    beta-firmware-1.x/net5501/ver
    beta-firmware-1.x/net5501/astlinux-1.0-5260.tar.gz.sha1
    beta-firmware-1.x/net5501/astlinux-1.0-5260.tar.gz
    beta-firmware-1.x/geni586-serial
    beta-firmware-1.x/geni586-serial/ver
    beta-firmware-1.x/geni586-serial/astlinux-1.0-5256.tar.gz.sha1
    beta-firmware-1.x/geni586-serial/astlinux-1.0-5256.tar.gz

The "ver" file contents is 'astlinux-1.0-5260' and 'astlinux-1.0-5256', (without quotes) respectively.  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:
  http://bla-bla.tld/beta-firmware-1.x
then use the System Tab to upgrade.

Or from the CLI...

    upgrade-run-image check http://bla-bla.tld/beta-firmware-1.x
    
    upgrade-run-image upgrade http://bla-bla.tld/beta-firmware-1.x

You can manage as many repos as you wish.  For example:
  http://bla-bla.tld/firmware-1.x
might be used for production images.