Images

Currently available images.
You can reference these (along with the associated md5sum in your device boot configurations).

How to translate this images into boot config?

Easy/New way

Use the INFO field to update the configuration in one go: Example:

APIKEY=your_api_key_goes_here
account_device_config_update.sh -k ${API_KEY} -i -ipkg ${INFO}

More about the account_device_config_update.sh script here

Legacy way

Translate the given shell variables into something you can use against the cattlepi api to program the boot target for specific devices.

Example:

APIKEY=your_api_key_goes_here
PAYLOAD='{"config":{"autoupdate":true,"ssh":{"pi":{"authorized_keys":["'$(head -1 $HOME/.ssh/id_rsa.pub)'"]}}},"initfs":{"md5sum":"'${INITFSMD5}'", "url":"'${INITFS}'"},"rootfs":{"md5sum":"'${ROOTFSMD5}'","url":"'${ROOTFS}'"}}'
curl -H "Accept: application/json" \
    -H "Content-Type: application/json" \
    -H "X-Api-Key: $API_KEY" \
    -X POST -d "$PAYLOAD" \
    https://api.cattlepi.com/boot/default/config

Available prebuilt recipe images

There are 3 recipes that get automatically build periodically. These include:

raspbian_cattlepi
This is the default Cattlepi image
Recipe for this is: here
To build this yourself: make raspbian_cattlepi

raspbian_pihole This image has PiHole baked into it.
Recipe for this is: here
To build this yourself: make raspbian_pihole

raspbian_stock This image will write place stock raspbian on your SDCard (need the SD card to be in a compatible layout or you need to associate the proper sdlayout to enable it)
Recipe for this is: here
To build this yourself: make raspbian_stock

In general all the images that are referenced by the API will be preserved and the ones that are not in use will be garbage collected periodically. If you want to ensure that the image you are using is not removed be sure to reference it in a configuration or persist it somewhere else and after that reference it from there.

The current prebuilt available images

For each set of images there is a build id (that captures a timestamp) and underneath that build id you have the pointers and the checksums for the images themselves.

2019_06_22_172451
  
  raspbian_cattlepi
    # generated on Sat 22 Jun 17:54:21 BST 2019
    INFO=https://api.cattlepi.com/images/global/autobuild/raspbian_cattlepi/2019_06_22_172451/info.sh
    INITFS=https://api.cattlepi.com/images/global/autobuild/raspbian_cattlepi/2019_06_22_172451/initramfs.tgz
    INITFSMD5=2e734def92d9a326985fd98658cb91ef
    ROOTFS=https://api.cattlepi.com/images/global/autobuild/raspbian_cattlepi/2019_06_22_172451/rootfs.sqsh
    ROOTFSMD5=ece1bc4467756f5e77dc4a02d632e42c
  
  raspbian_stock
    # generated on Sat 22 Jun 19:03:24 BST 2019
    INFO=https://api.cattlepi.com/images/global/autobuild/raspbian_stock/2019_06_22_172451/info.sh
    INITFS=https://api.cattlepi.com/images/global/autobuild/raspbian_stock/2019_06_22_172451/initramfs.tgz
    INITFSMD5=11ffb3b97324f5bf79af9c52649db77f
    ROOTFS=https://api.cattlepi.com/images/global/autobuild/raspbian_stock/2019_06_22_172451/rootfs.sqsh
    ROOTFSMD5=d8fb2bd9699fa7410dcec59cf914c6eb
  
  

Build your own images

Learn how to build your own images here: BUILDING.md