# HG changeset patch # User Sebastien Jodogne # Date 1481648415 -3600 # Node ID 83c0a6556e6c35eddad3f7ab9a8dabf9330fdf48 # Parent 9c295f7cc01659d949ac173725eb71a0a67abf47 Orthanc 1.2.0 diff -r 9c295f7cc016 -r 83c0a6556e6c Sphinx/source/developers/db-versioning.rst --- a/Sphinx/source/developers/db-versioning.rst Mon Dec 12 16:44:47 2016 +0100 +++ b/Sphinx/source/developers/db-versioning.rst Tue Dec 13 18:00:15 2016 +0100 @@ -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.1.0 u u u x +Orthanc 0.9.5 - Orthanc 1.2.0 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 9c295f7cc016 -r 83c0a6556e6c Sphinx/source/dicom-guide.rst --- a/Sphinx/source/dicom-guide.rst Mon Dec 12 16:44:47 2016 +0100 +++ b/Sphinx/source/dicom-guide.rst Tue Dec 13 18:00:15 2016 +0100 @@ -241,7 +241,7 @@ application that handles patients from different hospitals. *Note:* The current version of the :ref:`Orthanc Explorer -` interface (1.1.0 at the time of writing) is +` interface (1.2.0 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.1.0, C-Get is not supported yet (but work is in +As of Orthanc 1.2.0, C-Get is not supported yet (but work is in progress). *Note 2:* As :ref:`written above `, the Orthanc diff -r 9c295f7cc016 -r 83c0a6556e6c Sphinx/source/faq/log.rst --- a/Sphinx/source/faq/log.rst Mon Dec 12 16:44:47 2016 +0100 +++ b/Sphinx/source/faq/log.rst Tue Dec 13 18:00:15 2016 +0100 @@ -25,7 +25,7 @@ 2. Stop the Orthanc service. The actual process depends on your version of Windows. -3. Copy the just-downloaded ``Orthanc-1.1.0-Release.exe`` together +3. Copy the just-downloaded ``Orthanc-1.2.0-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``). @@ -33,7 +33,7 @@ 4. Type in a command-line shell, to generate the ``Orthanc.log`` file:: $ cd C:\Temp - $ Orthanc-1.1.0-Release.exe --verbose Configuration.json > Orthanc.log 2<&1 + $ Orthanc-1.2.0-Release.exe --verbose Configuration.json > Orthanc.log 2<&1 5. Restart the Orthanc service. diff -r 9c295f7cc016 -r 83c0a6556e6c Sphinx/source/faq/troubleshooting.rst --- a/Sphinx/source/faq/troubleshooting.rst Mon Dec 12 16:44:47 2016 +0100 +++ b/Sphinx/source/faq/troubleshooting.rst Tue Dec 13 18:00:15 2016 +0100 @@ -43,7 +43,7 @@ performance, make sure to use either the mainline version of the container (run ``docker pull jodogne/orthanc`` to ensure you use the most recent version of the mainline), or versions more recent than - ``jodogne/orthanc:1.1.0``. + ``jodogne/orthanc:1.2.0``. * **Orthanc slows down if storing many files**: The default database engine that is built in Orthanc is `SQLite diff -r 9c295f7cc016 -r 83c0a6556e6c Sphinx/source/users/configuration.rst --- a/Sphinx/source/users/configuration.rst Mon Dec 12 16:44:47 2016 +0100 +++ b/Sphinx/source/users/configuration.rst Tue Dec 13 18:00:15 2016 +0100 @@ -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 9c295f7cc016 -r 83c0a6556e6c Sphinx/source/users/docker.rst --- a/Sphinx/source/users/docker.rst Mon Dec 12 16:44:47 2016 +0100 +++ b/Sphinx/source/users/docker.rst Tue Dec 13 18:00:15 2016 +0100 @@ -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.1.0 + $ sudo docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc:1.2.0 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.1.0 + $ sudo docker run -p 4242:4242 -p 8042:8042 --rm -v /tmp/orthanc-db/:/var/lib/orthanc/db/ jodogne/orthanc:1.2.0 Whole-slide imaging support