Docs
Intro
Install
- Gem
  - Multiple Versions
  - Custom Version
- Ruby
- Shim
- Updating
Blueprints
- Structure
- Lookups
Config
- App
- Logging
- Params
- Variables
- Boot Hooks
- Lifecycle Hooks
  - Usage
  - Generator
  - Ruby
- Stack Name
- Initializers
- Restricting
  - Envs
  - Regions
- Seed
  - Authoring
- Reference
Generators
Layering
DSL
- Basics
  - Format Version
  - Condition
  - Description
  - Mapping
  - Metadata
  - Output
  - Parameter
  - Resource
  - Section
  - Transform
- Advanced
- Intrinsic Functions
  - Base64
  - Cidr
  - Condition Functions
  - FindInMap
  - GetAtt
  - GetAZs
  - ImportValue
  - Join
  - Ref
  - Select
  - Split
  - Sub
Helpers
- Built-In
- Custom
  - Blueprint
  - Project
Lonofile
- Usage
- Options
- Sources
  - Git
  - S3
  - GCS
  - Local
  - SSH
- Version Locking
- Terraform Notation
- Env Vars
Configsets
- DRY
- Usage
- Configure
  - Project
  - Blueprint
- Structure
- DSL
  - package
  - group
  - user
  - source
  - file
  - command
  - service
  - configset
- ERB
- Helpers
  - Built-In Helpers
    - Content File
  - Custom
- Variables
- Layering
- Pros and Cons
- cfn-init vs cloud-init
- cfn-init vs user-data
- Lookups
- Debugging Tips
More
Upgrading
- Version 8
Next Steps
CLI Reference

Conventions

Lono follows a set of naming conventions to encourage best practices in a naming scheme. This also dramatically allows lono commands to be shorter and hopefully more memorable.

Getting Started

Docs

sidebar options:

Conventions