Basic CLI infrastructure about tt HOT 7 CLOSED

I think that tt should get information about the location of external modules through the config, which by default it searches in the same directory (or the location of the config can be passed through an argument / environment variable). The config should describe the name of the module and its parameters. For example:

{
	name_of_module: {
		path: path/to/module,
		type: type_of_the_module
	},
	name_of_module_2: {
		path: path/to/module_2,
		type: type_of_the_module
	}
}

But it may be easier and user friendly to specify in the config only the path to the directory with the modules, and take the module name from the file names or "ask" the module.

from tt.

For mercurial, the full path to the extension is specified if it is not located in the "standard" path. (https://www.mercurial-scm.org/wiki/UsingExtensions)

from tt.

from tt.

I think that tt should get information about the location of external modules through the config, which by default it searches in the same directory (or the location of the config can be passed through an argument / environment variable). The config should describe the name of the module and its parameters. For example:

{
	name_of_module: {
		path: path/to/module,
		type: type_of_the_module
	},
	name_of_module_2: {
		path: path/to/module_2,
		type: type_of_the_module
	}
}

But it may be easier and user friendly to specify in the config only the path to the directory with the modules, and take the module name from the file names or "ask" the module.

I think it would be nice

1. To get plugins dir list from .tt.conf (default value: /usr/lib/tt/plugins for the system and ./tt/plugins for local)
2. To separate module types by thier file types, for example: file.plugin - is a plugin, the other - is the other
3. If a module is represented twice, type plugin has the lowest priority.

from tt.

Tarantool ticket tarantool/tarantool#6211 to provide local start

from tt.

rename .tt.conf to tarantool.yaml

from tt.

• find tarantool.yaml - a bundle cofig (from $CURDIR upto /). If the config doesn't exists let's think that $CURDIR is a base bundle path)

Why do we want to use this kind of search logic? I understand if we search a config in the current directory, home, /etc/tt, but why we want to search a config in/?

from tt.