testing_project/Documentation: book/admin/start_stop_instance — Russian @ Weblate: $ systemctl start tarantool@my_app $ ps axuf|grep my

The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.

Zen

Translation

English

Russian

Needs editing

Skip

	English	Russian	Actions
	Run ``tt init`` in this directory:
	$ tt init • Environment config is written to 'tt.yaml'
	This command creates a default ``tt`` configuration file ``tt.yaml`` for a local environment and the directories for instance files, control sockets, logs, and other artifacts:
	$ ls bin distfiles include instances.enabled modules templates tt.yaml
	To run a Tarantool instance in the local environment:
	Place the instance file into the ``instances.enabled/`` directory inside the current directory.
	$ tt start
	After the instance is started, you can find its artifacts in their locations inside the current directory:
	logs in ``var/log/<instance_name>``
	snapshots and write-ahead logs in ``var/lib/<instance_name>``
	control sockets and PID files in ``var/run/<instance_name>``
	To work with a local environment from a directory outside it, issue ``tt`` calls with the ``-L`` or ``--local`` argument with the path to this environment as its value:
	$ tt --local=/usr/tt/env/ start
	Using systemd tools
	If you start an instance using ``systemd`` tools, like this (the instance name is ``my_app``):	При запуске экземпляра с помощью инструментария ``systemd`` указанным ниже способом (имя экземпляра -- ``my_app``):
	$ systemctl start tarantool@my_app $ ps axuf\|grep my_app taranto+ 5350 1.3 0.3 1448872 7736 ? Ssl 20:05 0:28 tarantool my_app.lua <running>	$ systemctl start tarantool@my_app $ ps axuf\|grep my_app taranto+ 5350 1.3 0.3 1448872 7736 ? Ssl 20:05 0:28 tarantool my_app.lua <running>
	This actually calls ``tarantoolctl`` like in case of ``tarantoolctl start my_app``.	...на самом деле вызывается ``tarantoolctl`` -- так же, как и в случае ``tarantoolctl start my_app``.
	To enable ``my_app`` instance for auto-load during system startup, say:	Для включения автоматической загрузки экземпляра ``my_app`` при запуске всей системы используйте команду:
	$ systemctl enable tarantool@my_app	$ systemctl enable tarantool@my_app
	To stop a running ``my_app`` instance with ``systemctl``, run:	Для остановки работающего экземпляра ``my_app`` используйте команду:
	$ systemctl stop tarantool@my_app	$ systemctl enable tarantool@my_app
	To restart a running ``my_app`` instance with ``systemctl``, run:	Для остановки работающего экземпляра ``my_app`` используйте команду:
	$ systemctl restart tarantool@my_app	$ systemctl enable tarantool@my_app