-
Notifications
You must be signed in to change notification settings - Fork 43
[3pt] Set box.cfg options via environment variables #2066
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
For an example of variable precedence, see https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable |
veod32
added a commit
that referenced
this issue
Feb 23, 2022
veod32
added a commit
that referenced
this issue
Feb 24, 2022
This was referenced Feb 24, 2022
veod32
added a commit
that referenced
this issue
Feb 27, 2022
Add the new section describing setting box.cfg parameters via environment variables Closes #2066
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Set box.cfg options via environment variables
Product: Tarantool
Since: 2.8.1
Audience/target: all Tarantool users
Root document:
SME: @ romanhabibov
Details
The name of variable should correspond the following pattern:
TT_<NAME>
, where<NAME>
is uppercase box.cfg option name. Forexample:
TT_LISTEN
,TT_READAHEAD
.Array values are separated by comma. Example:
export TT_REPLICATION=localhost:3301,localhost:3302
An empty variable is the same as unset one.
started under tarantoolctl utility, environment variables have higher
priority than tarantoolctl configuration file.
Definition of done
The text was updated successfully, but these errors were encountered: