# HG changeset patch # User Sebastien Jodogne # Date 1531832870 -7200 # Node ID 07dc35042826a485222e1d4c3da1f34c9f27ffff # Parent 80b39dfa1e3c52ffcaf18b0f982c00f1a1dfbf8d Orthanc 1.4.1 diff -r 80b39dfa1e3c -r 07dc35042826 Sphinx/source/developers/db-versioning.rst --- a/Sphinx/source/developers/db-versioning.rst Fri Jul 13 16:20:59 2018 +0200 +++ b/Sphinx/source/developers/db-versioning.rst Tue Jul 17 15:07:50 2018 +0200 @@ -26,7 +26,7 @@ Version DB v2 DB v3 DB v4 DB v5 DB v6 =============================== ===== ===== ===== ===== ===== Mainline u u u x -Orthanc 0.9.5 - Orthanc 1.4.0 u u u x +Orthanc 0.9.5 - Orthanc 1.4.1 u u u x Orthanc 0.8.5 - Orthanc 0.9.4 u u x Orthanc 0.7.3 - Orthanc 0.8.4 u x Orthanc 0.4.0 - Orthanc 0.7.2 x diff -r 80b39dfa1e3c -r 07dc35042826 Sphinx/source/dicom-guide.rst --- a/Sphinx/source/dicom-guide.rst Fri Jul 13 16:20:59 2018 +0200 +++ b/Sphinx/source/dicom-guide.rst Tue Jul 17 15:07:50 2018 +0200 @@ -241,7 +241,7 @@ application that handles patients from different hospitals. *Note:* The current version of the :ref:`Orthanc Explorer -` interface (1.4.0 at the time of writing) is +` interface (1.4.1 at the time of writing) is designed for single-hospital scenarios, and thus does not provide study-level access. But the core engine of Orthanc does support study-level access through its :ref:`REST API `. @@ -572,7 +572,7 @@ server. The DICOM standard features an `alternative mechanism called C-Get `_. -As of Orthanc 1.4.0, C-Get is not supported yet (but work is in +As of Orthanc 1.4.1, C-Get is not supported yet (but work is in progress). *Note 2:* As :ref:`written above `, the Orthanc diff -r 80b39dfa1e3c -r 07dc35042826 Sphinx/source/faq/log.rst --- a/Sphinx/source/faq/log.rst Fri Jul 13 16:20:59 2018 +0200 +++ b/Sphinx/source/faq/log.rst Tue Jul 17 15:07:50 2018 +0200 @@ -49,7 +49,7 @@ 2. Stop the Orthanc service. The actual process depends on your version of Windows. -3. Copy the just-downloaded ``Orthanc-1.4.0-Release.exe`` together +3. Copy the just-downloaded ``Orthanc-1.4.1-Release.exe`` together with your configuration file (that is by default located in ``C:\Orthanc\Configuration.json``) into the same folder (e.g. ``C:\Temp``). @@ -57,7 +57,7 @@ 4. Type in a command-line shell, to generate the ``Orthanc.log`` file:: $ cd C:\Temp - $ Orthanc-1.4.0-Release.exe --verbose Configuration.json > Orthanc.log 2<&1 + $ Orthanc-1.4.1-Release.exe --verbose Configuration.json > Orthanc.log 2<&1 5. Restart the Orthanc service. diff -r 80b39dfa1e3c -r 07dc35042826 Sphinx/source/users/configuration.rst --- a/Sphinx/source/users/configuration.rst Fri Jul 13 16:20:59 2018 +0200 +++ b/Sphinx/source/users/configuration.rst Tue Jul 17 15:07:50 2018 +0200 @@ -6,7 +6,7 @@ Configuring Orthanc simply consists in copying and adapting the `default configuration file -`_. This +`_. This file is in the `JSON `_ file format. You can generate a sample configuration file with the following call:: diff -r 80b39dfa1e3c -r 07dc35042826 Sphinx/source/users/docker.rst --- a/Sphinx/source/users/docker.rst Fri Jul 13 16:20:59 2018 +0200 +++ b/Sphinx/source/users/docker.rst Tue Jul 17 15:07:50 2018 +0200 @@ -45,7 +45,7 @@ If more stability is required, you can select the official release of Orthanc to be run:: - $ sudo docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc:1.4.0 + $ sudo docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc:1.4.1 Passing additional command-line options (e.g. to make Orthanc verbose) can be done as follows (note the ``/etc/orthanc`` option that is @@ -94,7 +94,7 @@ container to some path in the filesystem of your Linux host, e.g.:: $ mkdir /tmp/orthanc-db - $ sudo docker run -p 4242:4242 -p 8042:8042 --rm -v /tmp/orthanc-db/:/var/lib/orthanc/db/ jodogne/orthanc:1.4.0 + $ sudo docker run -p 4242:4242 -p 8042:8042 --rm -v /tmp/orthanc-db/:/var/lib/orthanc/db/ jodogne/orthanc:1.4.1 Whole-slide imaging support