Commands
Reference guide for the command-line interface
Since Talos is a command-line program, functionality is invoked by it's various available subcommands.
run— Execute a script/project with Talos.tasks— Runs pre-defined crate manifest tasks.test— Runs all available unit tests with Talos.bundle— Bundles scripts/projects into executables.format— Formats scripts/projects with the builtin styler.lint— Lints scripts/projects for enhanced static analysis.upgrade— Upgrades to the latest version of Talos available.
Additionally, the following flags retrieve additional information about the runtime.
# Shows the usage prompt for Talos
talos --help
# Gets the current executable version
talos --version
# Lists all the vendors used by Talos
talos --vendorsEnvironment Variables (Internal)
The following environment variables are available across all subcommands.
TALOS_LOGGING_LEVEL
This variable allows setting the debug logging level, which can provide additional debugging information for the underlying runtime and subcommands. It can be one of theses levels: trace, debug, warn, error, fatal and is currently preset to warn.
TALOS_HARDWARE_VPROCS
This variable allows declaring the total underlying virtual processors to be used. By default, Talos will use the maximum available hardware processors.
# A arbitrary number can be used.
export TALOS_HARDWARE_VPROCS=8
# This forces Talos into a "single-threaded" mode.
export TALOS_HARDWARE_VPROCS=1
# For when you want to ensure the maximum processors.
export TALOS_HARDWARE_VPROCS=0Note:
Although Talos can be ran in a single-threaded context, additional threads will still be used internally for type-analysis and garbage collection.
Environment Variables (External)
NO_COLOR
Talos is shipped with the informal NO_COLOR standard. This environment variable can be assigned a value other than 0 to disable all colored outputs. Furthermore, this will also forcibly toggle the enablement of the builtin ANSI crate.
NO_PROGRESS
Talos is shipped with the informal NO_PROGRESS standard. This environment variable can be assigned a value other than 0 to disable all spinners and progress bars. This is particularly useful for logging testing results without distortions in non-terminal contexts.