{"id":20564342,"url":"https://github.com/tarantool/tt","last_synced_at":"2026-02-26T12:07:36.450Z","repository":{"id":37283164,"uuid":"355197173","full_name":"tarantool/tt","owner":"tarantool","description":"Command-line utility to manage Tarantool applications","archived":false,"fork":false,"pushed_at":"2026-02-18T14:58:05.000Z","size":3862,"stargazers_count":110,"open_issues_count":170,"forks_count":17,"subscribers_count":11,"default_branch":"master","last_synced_at":"2026-02-18T15:16:00.188Z","etag":null,"topics":["cli","go","tarantool"],"latest_commit_sha":null,"homepage":"","language":"Go","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/tarantool.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2021-04-06T13:23:57.000Z","updated_at":"2026-02-18T10:41:14.000Z","dependencies_parsed_at":"2023-09-27T15:28:07.964Z","dependency_job_id":"cde7f7e5-566b-4d04-9a76-b4fb0a335d8c","html_url":"https://github.com/tarantool/tt","commit_stats":null,"previous_names":[],"tags_count":36,"template":false,"template_full_name":null,"purl":"pkg:github/tarantool/tt","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tarantool%2Ftt","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tarantool%2Ftt/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tarantool%2Ftt/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tarantool%2Ftt/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/tarantool","download_url":"https://codeload.github.com/tarantool/tt/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tarantool%2Ftt/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29858465,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-26T08:51:08.701Z","status":"ssl_error","status_checked_at":"2026-02-26T08:50:19.607Z","response_time":89,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["cli","go","tarantool"],"created_at":"2024-11-16T04:25:51.639Z","updated_at":"2026-02-26T12:07:36.441Z","avatar_url":"https://github.com/tarantool.png","language":"Go","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003c!-- spell-checker:ignore testfull --\u003e\n\n\u003ca href=\"http://tarantool.org\"\u003e\n  \u003cimg src=\"https://avatars2.githubusercontent.com/u/2344919?v=2\u0026s=250\"\n  align=\"right\" alt=\"Tarantool logo\"\u003e\n\u003c/a\u003e\n\n# Tarantool CLI\n\n[![Go Reference][godoc-badge]][godoc-url]\n[![Go Report][report-badge]][report-url]\n[![Release][release-badge]][release-url]\n[![Full CI][testing-actions-badge]][testing-actions-url]\n\nTarantool CLI - command line utility for managing Tarantool packages and\nTarantool-based applications.\n\n## Contents\n\n- [Intro](#intro)\n- [Getting started](#getting-started)\n  + [Installation](#installation)\n  + [Build from source](#build-from-source)\n    * [Prerequisites](#prerequisites)\n    * [Build](#build)\n    * [Dependencies](#dependencies)\n    * [Run tests](#run-tests)\n- [Configuration](#configuration)\n  + [Configuration file](#configuration-file)\n- [Creating tt environment](#creating-tt-environment)\n- [External modules](#external-modules)\n- [CLI Args](#cli-args)\n  + [Autocompletion](#autocompletion)\n- [TT usage](#tt-usage)\n  + [Working with a set of instances](#working-with-a-set-of-instances)\n  + [Working with application templates](#working-with-application-templates)\n  + [Working with tt daemon (experimental)](#working-with-tt-daemon-experimental)\n  + [Setting Tarantool configuration parameters via environment variables](#setting-tarantool-configuration-parameters-via-environment-variables)\n  + [Add current environment binaries location to the PATH variable](#add-current-environment-binaries-location-to-the-path-variable)\n- [Migration from older TT versions](doc/migration_from_older_versions.md)\n- [Known issues](doc/known_issues.md)\n- [Commands](#commands)\n\n## Intro\n\n`tt` is tarantool's instance and environment management utility and is used to\ndevelop, deploy, run and operate applications.\n\nOne of the basic concepts that `tt` introduces is \"environment\".\nThe \"environment\" is an isolated workspace for the tarantool application suite.\n[`tt.yaml` configuration file](#configuration) defines the root and\nconfiguration of the *environment*. When `tt` is installed from a repository by\na package manager (`apt`, `rpm`, ...) a \"system\" config file\n(`/etc/tarantool/tt.yaml`) is included which forms the \"system\" environment -\nthe case when `tt` replaces the [`tarantoolctl`](https://github.com/tarantool/tt/blob/master/doc/examples.md#transition-from-tarantoolctl-to-tt).\nIn case we want to form a local environment (very convenient during\ndevelopment), we use a \"local\" `tt.yaml` generated with the [`tt init`](#creating-tt-environment)\ncommand. In this way, the user/developer can have a large number of different\n\"environments\" in the system in which different versions of both\n`tarantool`/`tt` and the applications being developed will be used.\n\nThe example of a typical \"environment\":\n\n```mermaid\ngraph LR\n    %% Colors %%\n    classDef lime fill:#C7EA46,stroke:#000,color:#000\n\n    subgraph dot[Environment root]\n      config\n      bin\n      modules\n      local_reps\n      inst_enabled[instances.enabled]\n    end\n    subgraph local_reps[Local repositories]\n      dist[distfiles]\n      rocks[rocks]\n    end\n    subgraph app1_files[Application]\n        app_dir[app]\n        app_dir --\u003e init(init.lua):::lime\n        app_dir --\u003e |multi-instance|instances(instances.yaml):::lime\n        app_dir --\u003e |3.0|cluster_config(config.yaml):::lime\n        app_dir --\u003e var[var]\n        var --\u003e run[run] --\u003e inst11[instance]\n        inst11 --\u003e pid1(tt.pid):::lime\n        inst11 --\u003e control1(tarantool.control):::lime\n        inst11 --\u003e binary1(tarantool.sock):::lime\n\n        var --\u003e log1[log] --\u003e inst12[instance] --\u003e logfile1(tt.log):::lime\n\n        var --\u003e lib1[lib] --\u003e inst13[instance]--\u003e xlogs1(*.xlog,*.snap):::lime\n    end\n\n    root[.] --\u003e config(tt.yaml):::lime\n\n    bin --\u003e bin_dir(tarantool\u003cbr/\u003etarantool-ee\u003cbr/\u003ett-ee\u003cbr/\u003ett):::lime\n    root --\u003e bin[bin]\n\n    modules --\u003e modules_dir(ext_module_1\u003cbr/\u003eext_module_2):::lime\n    root --\u003e modules[modules]\n\n    root --\u003e dist\n    root --\u003e rocks\n    inst_enabled --\u003e app_dir\n```\n\n## Getting started\n\n### Installation\n\nTT can be installed from the deb / rpm repository \"tarantool/modules\".\n\nInstall the tarantool repositories:\n\n\u003chttps://www.tarantool.io/en/download/os-installation/\u003e\n\nInstall TT:\n\n- Deb based distributions:\n\n``` console\napt-get install tt\n```\n\n- Rpm based distributions:\n\n``` console\nyum install tt\ndnf install tt\n```\n\nOn Gentoo Linux, the TT can be installed from the [Tarantool Gentoo\nOverlay](https://github.com/tarantool/gentoo-overlay):\n\n``` console\nemerge tt\n```\n\nOn MacOS, the TT can be installed from brew:\n\n``` console\nbrew install tt\n```\n\nYou can also install Tarantool CLI by downloading archive with pre-built\nbinary for your OS from GitHub's Releases page.\n\nHowever, on MacOS to run that binary you will need to do additional\nsteps:\n\n1. After first try to run binary, you will encounter an error:\n\n    \u003cimg src=\"doc/images/macOS_error.jpeg\" width=\"250\" alt=\"MacOS error.\" /\u003e\n\n1. To fix it, you should go to 'system settings-\\\u003eprivacy and\n    security', then scroll down and find:\n\n    \u003cimg src=\"doc/images/macOS_settings.jpeg\" width=\"350\" alt=\"MacOS settings.\" /\u003e\n\n1. Click on 'Allow Anyway' and you should be able to use Tarantool Cli.\n\n### Build from source\n\n#### Prerequisites\n\n- [Go (version 1.18+)](https://golang.org/doc/install)\n- [Mage](https://magefile.org/)\n- [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)\n\nTo run tests:\n\n- [Python3](https://www.python.org/downloads/)\n- [pytest](https://docs.pytest.org/en/7.2.x/getting-started.html#get-started)\n- [ruff](https://pypi.org/project/ruff/)\n- [golangci-lint](https://golangci-lint.run/usage/install/#local-installation)\n- [lichen](https://github.com/uw-labs/lichen#install)\n- [docker](https://docs.docker.com/engine/install/)\n- [NodeJS](https://nodejs.org/en/download)\n- [CMake](https://cmake.org/install/)\n- [etcd 3+](https://etcd.io/docs/v3.5/install/)\n\n#### Build\n\n``` console\ngit clone https://github.com/tarantool/tt --recursive\ncd tt\n```\n\nYou can build a binary without OpenSSL and TLS support for development\npurposes:\n\n``` console\nTT_CLI_BUILD_SSL=no mage build\nmage build\n```\n\nYou can build a binary with statically linked OpenSSL. This build type\nis used for releases:\n\n``` console\nTT_CLI_BUILD_SSL=static mage build\n```\n\nFinally, you can build a binary with dynamically linked OpenSSL for\ndevelopment purposes:\n\n``` console\nTT_CLI_BUILD_SSL=shared mage build\n```\n\n#### Dependencies\n\n**tt rocks runtime dependencies:**\n\n- [curl](https://curl.se) or\n    [wget](https://www.gnu.org/software/wget/)\n- [zip](http://infozip.sourceforge.net/)\n- [unzip](http://infozip.sourceforge.net/)\n\n**tt install \u0026\u0026 search runtime dependencies:**\n\n- [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)\n\n#### Run tests\n\nDisable `etcd` service:\n\n``` console\nsystemctl stop etcd\nsystemctl disable etcd\n```\n\nCreate a virtual environment and install tests requirements:\n\n``` console\npython3 -m venv .venv\n\nsource .venv/bin/activate\n\npip install -r test/requirements.txt\n```\n\nOnce inside the virtual environment, run default set of tests (excluding\nslow tests):\n\n``` console\nmage test\n```\n\nTo run full set of tests:\n\n``` console\nmage testfull\n```\n\n### Commit changes\n\nThe project uses [pre-commit](https://pre-commit.com/) to check code before committing.\nAfter activating the virtual environment for [run tests](#run-tests), the `pre-commit`\nhooks must be installed in the repository:\n\n``` console\npre-commit install\n```\n\nNow you will perform automatic checks at every commit.\nThe first time you use `pre-commit` it will install the dependencies needed for\nit to work, which may take some time. Subsequent runs will be much faster.\n\nIf errors were found, the commit will fail. If the errors can be corrected\nautomatically, you will receive modified files to add to the commit, checking\nfor correctness. In other cases you will get a message with errors that need to\nbe corrected manually.\n\n## Configuration\n\nTarantool CLI can be launched in several modes:\n\n- System launch (flag `-S`) - the working directory is current,\n    configuration file searched in `/etc/tarantool` directory.\n- Local launch (flag `-L`) - the working directory is the one you\n    specified, configuration file is searched in this directory. If\n    configuration file doesn't exists, config searched from the working\n    directory to the root. If it is also not found, then take config\n    from `/etc/tarantool`. If tarantool or tt executable files are found\n    in working directory, they will be used further.\n- Default launch (no flags specified) - configuration file searched\n    from the current directory to the root, going down the directory\n    until file is found. Working directory - the one where the\n    configuration file is found. If configuration file isn't found,\n    config taken from `/etc/tarantool` directory. In this case working\n    directory is current.\n\n### Configuration file\n\nBy default, configuration file is named `tt.yaml`.\n\nYou can specify the path to the configuration file by using the `--cfg`\ncommand line option or by setting the `TT_CLI_CFG` environment variable.\nThe `TT_CLI_CFG` variable has a lower priority than the `--cfg` option.\n\nExample of configuration\nfile format:\n\n``` yaml\nenv:\n  instances_enabled: path/to/available/applications\n  bin_dir: path/to/bin_dir\n  inc_dir: path/to/inc_dir\n  restart_on_failure: bool\n  tarantoolctl_layout: bool\nmodules:\n  directory: path/to/modules/dir\napp:\n  run_dir: path/to/run_dir\n  log_dir: path/to/log_dir\n  wal_dir: var/lib\n  vinyl_dir: var/lib\n  memtx_dir: var/lib\nrepo:\n  rocks: path/to/rocks\n  distfiles: path/to/install\nee:\n  credential_path: path/to/file\ntemplates:\n  - path: path/to/templates_dir1\n  - path: path/to/templates_dir2\n```\n\n#### env\n\n- `instances_enabled` (string) - path to directory that stores all\n    applications.\n- `bin_dir` (string) - directory that stores binary files.\n- `inc_dir` (string) - directory that stores header files. The path\n    will be padded with a directory named include.\n- `restart_on_failure` (bool) - should it restart on failure.\n- `tarantoolctl_layout` (bool) - enable/disable tarantoolctl layout\n    compatible mode for artifact files: control socket, pid, log files.\n    Data files (wal, vinyl, snapshots) and multi-instance applications\n    are not affected by this option.\n\n#### modules\n\n- `directory` (string) - the path to directory where the external\n    modules are stored.\n\n#### app\n\n- `run_dir` (string) - path to directory that stores various instance\n    runtime artifacts like console socket, PID file, etc.\n- `log_dir` (string) - directory that stores log files.\n- `wal_dir` (string) - directory where write-ahead log (.xlog) files\n    are stored.\n- `memtx_dir` (string) - directory where memtx stores snapshot (.snap)\n    files.\n- `vinyl_dir` (string) - directory where vinyl files or subdirectories\n    will be stored.\n\n#### repo\n\n- `rocks` (string) - directory that stores rocks files.\n- `distfiles` (string) - directory that stores installation files.\n\n#### ee\n\n- `credential_path` (string) - path to file with credentials for\n    downloading tarantool-ee. File must contain login and password. Each\n    parameter on a separate line. Alternatively credentials can be set\n    via environment variables: `TT_CLI_EE_USERNAME` and `TT_CLI_EE_PASSWORD`.\n\n#### templates\n\n- `path` (string) - the path to templates search directory.\n\n## Creating tt environment\n\ntt environment can be created using `init` command:\n\n``` console\ntt init\n```\n\n`tt init` searches for existing configuration files in current\ndirectory:\n\n- `.cartridge.yml`. If `.cartridge.yml` is found, it is loaded, and\n    directory information from it is used for `tt.yaml` generation.\n- `.tarantoolctl`. If `.tarantoolctl` is found, it is invoked by\n    Tarantool and directory information from `default_cfg` table is used\n    for `tt.yaml` generation. `.tarantoolctl` will not be invoked by\n    `tt start` command, so all variables defined in this script will not\n    be available in application code.\n\nIf there are no existing configs in current directory, `tt init`\ngenerates default `tt.yaml` and creates a set of environment\ndirectories. Here is and example of the default environment filesystem\ntree:\n\n```text\n    .\n    ├── bin\n    ├── include\n    ├── distfiles\n    ├── instances.enabled\n    ├── modules\n    ├── tt.yaml\n    └── templates\n```\n\nWhere:\n\n- `bin` - directory that stores binary files.\n- `include` - directory that stores header files.\n- `distfiles` - directory that stores installation files for local\n    install.\n- `instances.enabled` - directory that stores enabled applications or\n    symlinks.\n- `modules` - the directory where the external modules are stored.\n- `tt.yaml` - tt environment configuration file generated by\n    `tt init`.\n- `templates` - the directory where external templates are stored.\n\n## External modules\n\nExternal module - any executable file stored in modules directory.\nModule must be able to handle `--description` and `--help` flags. When\ncalling with `--description` flag, module should print a short\ndescription of module to stdout. When calling with `--help` flag, module\nshould print a help information about module to stdout.\n\nTarantool CLI already contains a basic set of modules. You can overload\nthese with external ones, or extend functionality with your own module.\nModules getting from directory, which specified in `directory` field\n(see example above).\n\nFor example, you have an external `version` module. When you type\n`tt version`, the external `version` module will be launched. To run the\ninternal implementation, use the `--internal (-I)` flag. If there is no\nexecutable file with the same name, the internal implementation will be\nstarted.\n\nYou can use any external module that doesn't have any internal\nimplementation. For example, you have module named `example-module`.\nJust type `tt example-module` to run it.\n\nTo see list of available modules, type `tt -h`.\n\n## CLI Args\n\nArguments of Tarantool CLI:\n\n- `--cfg | -c` (string) - path to Tarantool CLI config.\n- `--internal | -I` - use internal module.\n- `--local | -L` (string) - run Tarantool CLI as local, in the\n    specified directory.\n- `--system | -S` - run Tarantool CLI as system.\n- `--help | -h` - help.\n\n### Autocompletion\n\nYou can generate autocompletion for `bash`, `zsh` and `fish` shell:\n\n``` sh\n. \u003c(tt completion bash)\n```\n\nEnter `tt`, press tab and you will see a list of available modules with\ndescriptions. Also, autocomplete supports external modules.\n\nFor commands, which argument is app or instance, autocompletion\nwill show suitable apps, in case of the pattern doesn't contain\ndelimiter `:`, and suitable instances otherwise.\n\nFor `tt create` command it will show a list of built-in templates and\ntemplates from the configuration file.\n\n## TT usage\n\n### Working with a set of instances\n\n`tt` can manage a set of instances based on one source file.\n\nTo work with a set of instances, you need: a directory where the files\nwill be located: `init.lua` and `instances.yml`.\n\n- `init.lua` - application source file.\n- `instances.yml` - description of instances.\n\nInstances are described in `instances.yml` with format:\n\n``` yaml\ninstance_name:\n  parameter: value\n```\n\nThe dot character in instance names is reserved for system use.\nAlso, if an instance name ends with `-stateboard`, it will be recognized\nas `stateboard`.\nIf it is necessary for a certain instance to work on a source file\nother than `init.lua`, then you need to create a script with a name in\nthe format: `instance_name.init.lua`.\n\nThe following environment variables are associated with each instance:\n\n- `TARANTOOL_APP_NAME` - application name (the name of the directory\n    where the application files are present).\n- `TARANTOOL_INSTANCE_NAME` - instance name.\n\n[Example](https://github.com/tarantool/tt/blob/master/doc/examples.md#working-with-a-set-of-instances)\n\n### Working with application templates\n\n`tt` can create applications from templates.\n\nTo work with application template, you need:\n\n- A `\u003cpath\u003e` where templates directories or archives are located.\n\n- `tt.yaml` configured to search templates in \\\u003cpath\\\u003e:\n\n    ``` yaml\n    templates:\n      - path: \u003cpath1\u003e\n      - path: \u003cpath2\u003e\n    ```\n\nApplication template may contain:\n\n- `*.tt.template` - template files, that will be instantiated during\n    application creation.\n- `MANIFEST.yaml` - template manifest (see details below).\n\nTemplate manifest `MANIFEST.yaml` has the following format:\n\n``` yaml\ndescription: Template description\nvars:\n    - prompt: User name\n      name: user_name\n      default: admin\n      re: ^\\w+$\n\n    - prompt: Retry count\n      default: \"3\"\n      name: retry_count\n      re: ^\\d+$\npre-hook: ./hooks/pre-gen.sh\npost-hook: ./hooks/post-gen.sh\ninclude:\n- init.lua\n- instances.yml\n```\n\nWhere:\n\n- `description` (string) - template description.\n- `vars` - template variables used for instantiation.\n  + `prompt` - user prompt for variable value input.\n  + `name` - variable name.\n  + `default` - default value of the variable.\n  + `re` - regular expression used for value validation.\n- `pre-hook` (string) - executable to run before template\n    instantiation.\n- `post-hook` (string) - executable to run after template\n    instantiation.\n- `include` (list) - list of files to keep in application directory\n    after create.\n\nThere are pre-defined variables that can be used in template text:\n`name` - application name. It is set to `--name` CLI argument value.\n\nDon't include the .rocks directory in your application template. To\nspecify application dependencies, use the .rockspec.\n\n[Custom template\nexample](https://github.com/tarantool/tt/blob/master/doc/examples.md#working-with-application-templates)\n\n### Working with tt daemon (experimental)\n\n`tt daemon` module is used to manage `tt` daemon on a given machine.\nThis way instances can be operated remotely. Daemon can be configured\nwith `tt_daemon.yaml` config.\n\n`tt_daemon.yaml` file format:\n\n``` yaml\ndaemon:\n      run_dir: path\n      log_dir: path\n      log_file: string (file name)\n      listen_interface: string\n      port: num\n      pidfile: string (file name)\n```\n\nWhere:\n\n- `run_dir` (string) - path to directory that stores various instance\n    runtime artifacts like console socket, PID file, etc. Default:\n    `run`.\n- `log_dir` (string) - directory that stores log files. Default:\n    `log`.\n- `log_file` (string) - name of file contains log of daemon process.\n    Default: `tt_daemon.log`.\n- `listen_interface` (string) - network interface the IP address\n    should be found on to bind http server socket. Default: loopback\n    (`lo`/`lo0`).\n- `port` (number) - port number to be used for daemon http server.\n    Default: 1024.\n- `pidfile` (string) - name of file contains pid of daemon process.\n    Default: `tt_daemon.pid`.\n\n[TT daemon\nexample](https://github.com/tarantool/tt/blob/master/doc/examples.md#working-with-tt-daemon-experimental)\n\n### Setting Tarantool configuration parameters via environment variables\n\nUsing `tt`, you can specify configuration parameters via special\nenvironment variables even on Tarantool versions that does not natively\nsupport it. The name of a variable should have the following pattern:\n`TT_\u003cNAME\u003e`, where `\u003cNAME\u003e` is the uppercase name of the corresponding\n[box.cfg](https://www.tarantool.io/en/doc/latest/reference/configuration/#box-cfg-params-ref)\nparameter.\n\n### Add current environment binaries location to the PATH variable\n\nYou can add current environment binaries location to the PATH variable:\n\n``` console\n. \u003c(tt env)\n```\n\nAlso TARANTOOL_DIR variable is set.\n\n## Commands\n\nCommon description. For a detailed description, use `tt help command` .\n\n- `start` - start a tarantool instance(s).\n- `stop` - stop the tarantool instance(s).\n- `status` - get current status of the instance(s).\n- `restart` - restart the instance(s).\n- `version` - show Tarantool CLI version information.\n- `completion` - generate autocomplete for a specified shell.\n- `help` - display help for any command.\n- `logrotate` - rotate logs of a started tarantool instance(s).\n- `check` - check an application file for syntax errors.\n- `connect` - connect to the tarantool instance.\n- `rocks` - LuaRocks package manager.\n- `cat` - print into stdout the contents of .snap/.xlog files.\n- `play` - play the contents of .snap/.xlog files to another Tarantool\n    instance.\n- `coredump` - pack/unpack/inspect tarantool coredump.\n- `run` - start a tarantool instance.\n- `search` - show available tt/tarantool versions.\n- `clean` - clean instance(s) files.\n- `create` - create an application from a template.\n- `build` - build an application.\n- `install` - install tarantool/tt.\n- `uninstall` - uninstall tarantool/tt.\n- `init` - create tt environment configuration file.\n- `daemon (experimental)` - manage tt daemon.\n- `cfg dump` - print tt environment configuration.\n- `pack` - pack an environment into a tarball/RPM/Deb.\n- `instances` - show enabled applications.\n- `binaries list` - show a list of installed binaries and their versions.\n- `binaries switch` - switch to installed binary.\n- `cluster` - manage cluster configuration.\n- `env` - add current environment binaries location to the PATH variable.\n- `replicaset` - manage replicasets.\n- `download` - download Tarantool SDK.\n- `enable` - create a symbolic link in 'instances_enabled' directory to a script\n   or an application directory.\n\n[godoc-badge]: https://pkg.go.dev/badge/github.com/tarantool/tt.svg\n[godoc-url]: https://pkg.go.dev/github.com/tarantool/tt\n\n[report-badge]: https://goreportcard.com/badge/github.com/tarantool/tt\n[report-url]: https://goreportcard.com/report/github.com/tarantool/tt\n\n[release-badge]: https://img.shields.io/github/v/release/tarantool/tt?include_prereleases\u0026label=Release\u0026labelColor=2d3532\n[release-url]: https://github.com/tarantool/tt/releases\n\n[testing-actions-badge]: https://github.com/tarantool/tt/actions/workflows/full-ci.yml/badge.svg?branch=master\n[testing-actions-url]: https://github.com/tarantool/tt/actions/workflows/full-ci.yml\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftarantool%2Ftt","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftarantool%2Ftt","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftarantool%2Ftt/lists"}