A ERB blueprint structure can look like this:
demo ├── app │ ├── definitions │ │ │── base.rb │ │ │── development.rb │ │ └── production.rb │ ├── helpers │ ├── partials │ ├── scripts │ ├── templates │ │ └── ec2.yml │ └── user_data ├── demo.gemspec ├── Gemfile ├── .meta │ └── config.yml └── setup └── configs.rb
|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
|demo.gemspec||Where the gem specs and dependencies are defined. Blueprints make use of the gem structure to handle dependencies.|
|.meta/config.yml||Where the blueprint_name and blueprint_type is set. The blueprint name is determined here; not the gem name.|
|seed/configs.rb||Where a setup script can be defined to work with
That hopefully gives you a basic idea of the blueprint directory structure.
Pro tip: Use the <- and -> arrow keys to move back and forward.