Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
T
tarantool
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
core
tarantool
Commits
39cd14e6
Commit
39cd14e6
authored
11 years ago
by
ocelot-inc
Browse files
Options
Downloads
Patches
Plain Diff
server.administration.xml add section about tarantool_deploy.sh
parent
56986d70
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/user/server-administration.xml
+44
-0
44 additions, 0 deletions
doc/user/server-administration.xml
with
44 additions
and
0 deletions
doc/user/server-administration.xml
+
44
−
0
View file @
39cd14e6
...
...
@@ -122,6 +122,50 @@ last xlog lsn: 0
</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_box server will start.
Technically, tarantool_deploy will place instructions in
<filename>
/etc/init.d
</filename>
which will initiate tarantool_box 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]
<
instance
>
--prefix
<
path
>
installation path (/usr)
--prefix_etc
<
path
>
installation etc path (/etc)
--prefix_var
<
path
>
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_box 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>
tarantool_deploy.sh 0.1
tarantool_deploy.sh: About to deploy Tarantool instance 0.1.
tarantool_deploy.sh: Continue? [n/y]
y
tarantool_deploy.sh:
>>>
deploy instance 0.1
tarantool_deploy.sh:
>>>
updating deployment config
tarantool_deploy.sh: done
</programlisting>
</para>
</section>
<section
xml:id=
"os-install-notes"
>
<title>
System-specific administration notes
</title>
<blockquote><para>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment