A basic lono project usually looks something like this:
├── app │ ├── definitions │ │ │── base.rb │ │ │── development.rb │ │ └── production.rb │ ├── helpers │ ├── partials │ ├── scripts │ ├── templates │ │ └── ec2.yml │ └── user_data ├── config │ ├── params │ │ ├── base │ │ │ └── ec2.txt │ │ └── production │ │ └── ec2.txt │ │── variables │ │ ├── base.rb │ │ └── production.rb │ └── settings.yml └── output
|File / Directory||Description|
|app/definitions||Here’s where you define or declare your template definitions. It tells lono what templates to generate to the
|app/helpers||Define your custom helpers here. The custom helpers are made available to
|app/partials||Where templates partials go. You can split up the CloudFormation templates into erb partials. Include them with the
|app/scripts||Where your custom scripts go. Scripts in this folder get uploaded to s3 as a tarball during the
|app/user_data||Where you place your scripts meant to be used for user-data. Include them in your templates with the
|config/params||Where you specific your run-time parameters for the CloudFormation stacks. Params files have access to shared variables and helpers also. The params are automatically layered together based on
|config/variables||This is where your shared variables that made are available
|output||This is where the generated files like CloudFormation templates and parameter files are written to. These files can be used with the raw
That hopefully gives you a basic idea for the lono directory structure.
That should give you a basic feel for the lono directory structure.
Pro tip: Use the <- and -> arrow keys to move back and forward.