Connect and configure your App using your existing container images, infrastructure as code, and DevOps automation.
<component name>.toml
file inside a directory called components
in the root of your App Config directory. e.g., a Helm chart Component named whoami
would be defined in a file named whoami.toml
inside a directory named components
.
Alternatively, you can nest individual Component files inside directories inside the components
directory. For example, you could have a directory named infra
inside the components
directory, and define an S3 Bucket Component named buckets.toml
.
Additional Component configuration files can be added to the components
directory or another directory in the App Config directory like src
, and referenced in the Component’s config file. e.g., you can have a values.yaml
file for a Helm chart Component located the root of the components
directory.
You can configure Components to use either a public repo (using a public_repo
block) or a private GitHub
repo (using a connected_repo
block). Read more about VCS configuration here.
git
repository to store its source files, but you can include them in the App Config directory and reference the same App Config repo in the Component TOML file. e.g., a Terraform Component named lamdba
that uses a variables.tf
file and Python code can be located in the App Config directory’s src
directory and referenced as the Public Repo in the Component’s config file:
nuon components --help
.
nuon apps select
before using the nuon components
commands, or pass the -a
flag to each
nuon component
command.nuon component
commands. This is helpful to avoid
having to pass -c
to each command.
nuon components select
first.-auto-build
flag which will trigger a
Build.
Create a Build - Create a Build using the latest Component configuration.