Mercurial > hg > orthanc-book

comparison Sphinx/source/users/docker.rst @ 1023:5d4701d8fe28

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
replaced osimis/orthanc by orthancteam/orthanc
author Alain Mazy <am@osimis.io>
date Thu, 01 Feb 2024 15:09:48 +0100
parents a3436ae3709c
children 60b0b7ea409b
comparison
equal deleted inserted replaced
1022:2969cbebbc91 1023:5d4701d8fe28
6 ============================= 6 =============================
7 7
8 .. toctree:: 8 .. toctree::
9 :hidden: 9 :hidden:
10 10
11 docker-osimis.rst 11 docker-orthancteam.rst
12 12
13 13
14 .. contents:: 14 .. contents::
15 :depth: 3 15 :depth: 3
16 16
22 for the Orthanc core and its official plugins are freely available on 22 for the Orthanc core and its official plugins are freely available on
23 the `DockerHub platform <https://hub.docker.com/u/jodogne/>`__. The 23 the `DockerHub platform <https://hub.docker.com/u/jodogne/>`__. The
24 source code of the corresponding Docker images is available on `GitHub 24 source code of the corresponding Docker images is available on `GitHub
25 <https://github.com/jodogne/OrthancDocker>`__. 25 <https://github.com/jodogne/OrthancDocker>`__.
26 26
27 **Note about Orthanc vs. Osimis Docker images:** 27 **Note about Orthanc vs. Orthanc Team Docker images:**
28 28
29 * The ``jodogne/orthanc`` and ``jodogne/orthanc-plugins`` Docker 29 * The ``jodogne/orthanc`` and ``jodogne/orthanc-plugins`` Docker
30 images that are described on this page are always kept in sync with 30 images that are described on this page are always kept in sync with
31 the latest releases of the Orthanc project, with a basic 31 the latest releases of the Orthanc project, with a basic
32 configuration system that is inherited from the Debian packages 32 configuration system that is inherited from the Debian packages
33 (i.e. manual edition of the configuration files). These images are 33 (i.e. manual edition of the configuration files). These images are
34 most useful to **software developers and researchers**. 34 most useful to **software developers and researchers**.
35 35
36 * Our commercial partner `Osimis <https://www.osimis.io>`__ also 36 * Our commercial partner `Orthanc Team <https://www.osimis.io>`__ also
37 `publishes separated Docker images 37 `publishes separated Docker images
38 <https://hub.docker.com/r/osimis/orthanc>`__. These 38 <https://hub.docker.com/r/orthancteam/orthanc>`__. These
39 ``osimis/orthanc`` images are used by the technical team of Osimis 39 ``orthancteam/orthanc`` images are used by the technical team of
40 in order to provide professional support to their customers, with a 40 the Orthanc Team company in order to provide professional support
41 to their customers, with a
41 configuration system that can be tuned through **environment 42 configuration system that can be tuned through **environment
42 variables** (which is very handy if using ``docker-compose`` or 43 variables** (which is very handy if using ``docker-compose`` or
43 Kubernetes). These images are not necessarily always in sync with 44 Kubernetes). A :ref:`specific page <docker-orthancteam>` is
44 the Orthanc project, but they also include the :ref:`plugins edited
45 by Osimis <plugins-osimis>`, notably the Osimis Web viewer (that is
46 much more advanced than the Orthanc Web viewer) and the advanced
47 authorization plugin. A :ref:`specific page <docker-osimis>` is
48 available to describe how these images should be used. These images 45 available to describe how these images should be used. These images
49 are targeted at **ops teams**. 46 are targeted at **ops teams**.
50 47
51 **Note for CentOS users:** The Docker environment might be difficult to 48 **Note for CentOS users:** The Docker environment might be difficult to
52 configure on your platform. Hints are available on the `Orthanc Users 49 configure on your platform. Hints are available on the `Orthanc Users