Starting Tarantool applications | Tarantool
Reference Tooling tt CLI utility Commands Starting Tarantool applications

Starting Tarantool applications


tt start starts Tarantool applications. The application files must be stored inside the instances_enabled directory specified in the tt configuration file. For detailed instructions on preparing and running Tarantool applications, see Application environment and Starting and stopping instances.

When called without arguments, starts all enabled applications in the current environment.

See also: Stopping a Tarantool instance, Restarting a Tarantool instance, Checking instance status.

tt start can start entire Tarantool clusters based on their YAML configurations. A cluster application directory inside instances_enabled must contain the following files:

  • config.yaml – a YAML configuration that defines the cluster topology and settings. It can either contain an explicit configuration in the YAML format or point to a centralized configuration storage (for Enterprise Edition).
  • instances.yml – a file that defines the list of cluster instances to run in the current environment.
  • (Optionally) *.lua files with code to load and run in the cluster.

For more information about Tarantool application layout, see Application environment.


tt also supports Tarantool applications with configuration in code, which is considered a legacy approach since Tarantool 3.0. For information about using tt with such applications, refer to the Tarantool 2.11 documentation.

tt start runs Tarantool applications in the background and uses its own watchdog process for status checks (tt status) and application stopping (tt stop).


Do not switch on the background mode using the cluster configuration (process.background: true in the YAML configuration) or code (box.cfg.background = true) in applications that you run with tt. If you start such an application with tt start, tt won’t be able to check the application status or stop it using the corresponding commands.

  • Start instances of the application stored in the app directory inside instances_enabled in accordance with its instances.yml:

    $ tt start app
  • Start the router instance of the app application:

    $ tt start app:router
Found what you were looking for?