You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[TBD--do we need this?] As described before, you can specify configuration parameters via environment variables
326
+
and then pass them to ``box.cfg{}`` by using the ``os.getenv()`` function (see the :ref:`example <index-init-example>`).
327
+
328
+
Starting from version :doc:`2.8.1 </release/2.8.1>`, you can specify such parameters [via environment variables] in much easier way.
329
+
330
+
[TBD] The name of a variable should have the following pattern: ``TT_<NAME>``,
314
331
where ``<NAME>`` is the uppercase name of the corresponding ``box.cfg`` option.
315
332
333
+
[TBD]--maybe give an example with the value, and only for tt_listen.
316
334
For example:
317
335
318
336
* ``TT_LISTEN``---corresponds to the ``box.cfg.listen`` option.
319
337
* ``TT_REPLICATION``---corresponds to the ``box.cfg.replication`` option..
320
338
321
-
Array values are separated by comma. Example:
339
+
[TBD] On Tarantool start and the ``box.cfg{}`` call, the values of the ``TT_<NAME>`` environment variables will be set for the corresponding configuration parameters.
340
+
[TBD] ?Note on priorities?
341
+
342
+
[TBD] Array values should be separated by comma without space:
[TBD] An empty variable (``TT_LISTEN=``) has the effect as an unset one [meaning that the corresponding configuration parameter won't be set when calling ``box.cfg{}``].
0 commit comments