Skip to content
Snippets Groups Projects
Commit 34a6bd84 authored by ocelot-inc's avatar ocelot-inc
Browse files

remove tarantool_deploy.sh

parent ac1f0ba0
No related branches found
No related tags found
No related merge requests found
......@@ -207,54 +207,6 @@ Explanatory notes about what tarantool displayed in the above example:
</section>
<section xml:id="tarantool_deploy">
<title>Utility <code>tarantool_deploy</code></title>
<para>
With tarantool_deploy one can set up so that, during system boot,
one or more instances of the tarantool server will start.
This utility is for use on Red Hat or CentOS where Tarantool
was installed using <code>rpm --install</code>.
</para>
<para>
Technically, tarantool_deploy will place instructions in <filename>/etc/init.d</filename>
which will initiate tarantool with appropriate options and
with settings that maximize resource usage.
The root password is necessary. These options are available,
as shown by <code>tarantool_deploy --help</code>:
<programlisting>
Tarantool deployment script: add more Tarantool instances.
usage: tarantool_deploy.sh [options] &lt;instance&gt;
--prefix &lt;path&gt; installation path (/usr)
--prefix_etc &lt;path&gt; installation etc path (/etc)
--prefix_var &lt;path&gt; installation var path (/var)
--status display deployment status
--dry don't create anything, show commands
--debug show commands
--yes don't prompt
--help display this usage
</programlisting>
</para>
<para>
The default prefixes (<filename>/usr</filename> and <filename>/etc</filename> and <filename>/var</filename>) are appropriate
if a Tarantool installation was done with default settings,
for example tarantool should be in <filename>/usr/bin</filename>.
The only necessary argument is the "instance", which is an
arbitrary numeric identification formatted as digit.digit.
The following is a sample run:
<programlisting><prompt>$ </prompt><userinput>tarantool_deploy.sh 0.1</userinput>
tarantool_deploy.sh: About to deploy Tarantool instance 0.1.
tarantool_deploy.sh: Continue? [n/y]
<userinput>y</userinput>
tarantool_deploy.sh: &gt;&gt;&gt; deploy instance 0.1
tarantool_deploy.sh: &gt;&gt;&gt; updating deployment config
tarantool_deploy.sh: done
</programlisting>
</para>
</section>
<section xml:id="os-install-notes">
<title>System-specific administration notes</title>
<blockquote><para>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment