# HG changeset patch # User Alain Mazy # Date 1587544994 -7200 # Node ID 20003fa56bdf53cbf3072abf36a58cc2ae094d97 # Parent 7d219d619fb0052933dd9721c1ce61e8b0ec3604# Parent 18ef1c795d17d6fa80e578e65ba0950fedc27b8d merge diff -r 18ef1c795d17 -r 20003fa56bdf Sphinx/source/users/docker-osimis.rst --- a/Sphinx/source/users/docker-osimis.rst Wed Apr 22 08:58:30 2020 +0200 +++ b/Sphinx/source/users/docker-osimis.rst Wed Apr 22 10:43:14 2020 +0200 @@ -61,7 +61,7 @@ | DicomWeb.Servers | ORTHANC__DICOM_WEB__SERVERS | ``{"sample": [ "http://127.0.0.1/dicom-web/"]}`` | +---------------------------+----------------------------------------------+----------------------------------------------------------------+ -To find out a environment variable name from an Orthanc configuration +To find out an environment variable name from an Orthanc setting (i.e. ``DicomWeb.StudiesMetadata`` is the ``path`` to a setting): - everytime a word contains a capital letter, insert an underscore ``_`` in front. @@ -75,7 +75,7 @@ ``ORTHANC__DICOM_WEB__STUDIES_METADATA`` Note that, this automatic rule might fail because of 2 capital letters one after each other in some -Orthanc configurations. Therefore, there are some `exceptions `__ to this rule +Orthanc settings. Therefore, there are some `exceptions `__ to this rule that are however quite intuitive. Special environment variables @@ -156,7 +156,7 @@ .. highlight:: yaml When using your container in a ``Docker Swarm`` or ``Kubernetes`` environment, -it is usually to pass sensitive information through ``Docker Secrets``. +it is usually advised to pass sensitive information through ``Docker Secrets``. For this purpose, any secret whose name is similar to the name of an environment variable is considered as an environment variable::