You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, tt always requires a instances.yml file for multi-instance applications. This is fine for cartridge-based apps, but it can be inconvenient for Tarantool 3.x apps development. A Tarantool 3.x app already has a centralized configuration that contains a list of available instances, and all these instances should be listed in the instances.yml file. The idea is to use all the instances listed in the configuration, even if the instances.yml file is missing. If the user runs tt start, and there are too many instances in the config, tt will prompt for confirmation. During application distribution, the instances.yml could be generated to specify which instances to run.
The text was updated successfully, but these errors were encountered:
Currently,
tt
always requires ainstances.yml
file for multi-instance applications. This is fine for cartridge-based apps, but it can be inconvenient for Tarantool 3.x apps development. A Tarantool 3.x app already has a centralized configuration that contains a list of available instances, and all these instances should be listed in theinstances.yml
file. The idea is to use all the instances listed in the configuration, even if theinstances.yml
file is missing. If the user runstt start
, and there are too many instances in the config,tt
will prompt for confirmation. During application distribution, theinstances.yml
could be generated to specify which instances to run.The text was updated successfully, but these errors were encountered: