Presets¶
The Exasol Launcher uses presets to provision infrastructure and install the database. A preset is a self-contained directory of templates and configuration files.
Each deployment combines:
- an infrastructure preset, which provisions a cloud or local environment; and
- an installation preset, which installs and configures Exasol on that environment.
The built-in infrastructure presets are aws, azure, exoscale, stackit, and local. The
built-in ubuntu installation preset is selected by default where applicable.
List the built-in presets with:
Select a preset source¶
The install command accepts built-in names, filesystem paths, Git repositories, and archives:
exasol install <infrastructure-preset> [installation-preset]
exasol install aws
exasol install ./my-preset
exasol install https://github.com/org/preset.git
exasol install https://github.com/org/preset.git@v1.0
exasol install https://example.com/preset.tar.gz
exasol install file:///path/to/preset-dir
exasol install file:///path/to/preset.tar.gz
A local path starts with ., /, or ~, or otherwise contains a path separator. Local directory
URIs are used directly. Local archives are extracted again on each run.
Git sources support HTTPS and SSH URLs. Append @<branch-or-tag> to select a ref. The launcher
resolves the ref to a commit so that it can reuse the same content on later runs.
Remote .tar.gz, .tgz, and .zip archives can use HTTP or HTTPS. They are downloaded on each run
because the source does not supply a checksum.
Git repositories and archives accept an optional #<subpath> fragment. Use it to select a preset
from a subdirectory in a repository or multi-preset archive: