Skip to content
jaybuff edited this page Mar 10, 2011 · 2 revisions

Publishing Images

Joot will fetch all URLs listed in the images_sources section of your Configuration file. The format returned by each of those URLs must be a JSON file that looks like the below example.

Example

{
    "http://getjoot.org/images/darwin-10.6.0.x86-64.20110403.sparseimage.gz": {
        "root_partition": 2,
        "format": "sparseimage",
        "compression": "gzip"
    },
    "http://getjoot.org/images/ubuntu.10-10.x86-64.20101010.qcow.bz2": {
        "root_partition": 1,
        "format": "qcow",
        "compression": "bzip2"
    }
}

Top level keys are URLs to the image and the value is a data structure describing metadata about the image.

Metadata

key required description
format yes the format of the image
root_partition no If the image is a disk image, it may contain multiple partitions. This partition will be used for the joot.
compression no If the image is compressed, the compression algorithm used. The two valid values are bzip2 and gzip.

Local Images

If images live on your local machine you can reference them using the file:// scheme like below

{
    "file:///Users/jaybuff/images/darwin-10.6.0.x86-64.20110403.sparseimage": {
        "root_partition": 2,
        "format": "sparseimage"
}        

If the image is local joot will attempt to create a symbolic link rather than copying it in order to save disk. If the image is compressed this is not possible.

For local images you'll probably want to have image_sources section of your config file can contain entries such as file:///Users/jaybuff/images/index.js

Clone this wiki locally