Extensions Lookup Locations

Extensions allow you extend to the Lono DSL and can be shareable between multiple blueprints. Extensions are searched for in a few locations. It is similiar to how LOAD_PATH works.

Location Type Description
PROJECT/app/extensions project The project’s local extensions
PROJECT/vendor/extensions vendor Frozen vendor extensions
gems folder gem The gems folder is the location where the extension gem is installed. You can use bundle show GEM to reveal the location.
gems folder materialized All blueprint extensions will materialize if they are not found in the earlier lookup locations.

lono extensions BLUEPRINT command

The lono extensions BLUEPRINT command provides a quick way to find out what extensions are used by a specific blueprint.

$ lono extensions asg-worker
extensions used by asg-worker blueprint:
|     Name       |             Path              |  Type   |  From   |
| asg_extensions | app/extensions/asg_extensions | project | project |

Materialized Extensions

Blueprints can make use of extensions. Usually the extensions will be within your own project under app/extensions, vendor/extensions or in your Gemfile. If the extension used by the blueprint is not found in one of those locations, lono will materialize the extension and download it. These are known as “materialized” extensions.

Pro tip: Use the <- and -> arrow keys to move back and forward.

Edit this page

See a typo or an error? You can improve this page. This website is available on GitHub and contributions are encouraged and welcomed. We love pull requests from you!