Lonofile Usage


Here’s an example Lonofile.

blueprint "ec2",   source: "boltops-tools/ec2-blueprint"
configset "httpd", source: "boltops-tools/httpd-configset"
helper    "ec2",   source: "boltops-tools/ec2-extension"

Options Docs:

Additional Docs:


When you run:

lono bundle

The components in Lonofile are downloaded to the vendor folder.

A Lonofile.lock file is generated to lock component versions. You can then check in the lockfile into version control. Other members on your team running lono bundle will download the exact same versions as you.


To install the components, run:

$ lono bundle
Exporting vendor/blueprints/ec2
Exporting vendor/configsets/httpd
Exporting vendor/helpers/ec2

Components are downloaded to your vendor/blueprints, vendor/configsets, vendor/helpers folders. The components in vendor is sourced same way as if they were defined in app. This is because Lono considers multiple lookup paths. Docs: Lookup Paths


A Lonofile.lock file is also generated. This file can be committed to version control to ensure that everyone on the team uses the exact same version.


To update the Lonofile.lock with the latest versions.

lono bundle update

You can also selectively update multiple components.

lono bundle update blueprint1 configset2 extension3


You can list the components that installed from the Lonofile with:

$ lono bundle list
Components included by Lonofile.lock

|     Name      |   Type    |
| asg-extension | extension |
| httpd         | configset |
| vpc           | blueprint |

Use `lono bundle info` to print more detailed information about a component

Getting Info

You can get additional information about each bundled component with:

$ lono bundle info vpc
    sha: f8c0f95008f64a25461d9ff88ebd3e5ae1d4c785
    source: git@github.com:boltopspro/vpc
    source_type: git
    type: blueprint
    url: git@github.com:boltopspro/vpc