@@ -27,7 +27,7 @@ Install the PyGeometry image
2727
2828 .. code :: bash
2929
30- docker pull ghcr.io/pyansys/pygeometry :< tag>
30+ docker pull ghcr.io/pyansys/geometry :< tag>
3131
3232 The following OS-dependent tags are available:
3333
@@ -37,13 +37,65 @@ Install the PyGeometry image
3737Launching the Geometry service
3838------------------------------
3939
40+ In this section there are two mechanisms for launching the Geometry service: either **using the PyGeometry launcher **
41+ or **manually launching the service **.
42+
43+ Environment variables
44+ ^^^^^^^^^^^^^^^^^^^^^
45+
46+ The Geometry service has a set of environment variables that are **mandatory ** for its use:
47+
48+ * ``LICENSE_SERVER ``: the license server (IP, DNS) to which the Geometry service shall connect. For example, ``127.0.0.1 ``.
49+
50+ Other optional environment variables are:
51+
52+ * ``ENABLE_TRACE ``: whether to set up the trace level for debugging purposes. Expects either ``1 `` or ``0 ``.
53+ By default, ``0 `` (which means it is not activated).
54+ * ``LOG_LEVEL ``: sets the Geometry service logging level. By default, ``2 ``.
55+
56+ Depending on the mechanism chosen to launch the Geometry service, you can set them as follows:
57+
58+ .. tab-set ::
59+
60+ .. tab-item :: Using PyGeometry launcher
61+
62+ In this case, users will have to define the following general environment variables prior
63+ to launching it. Bare in mind that the naming of the variables is not the same:
64+
65+ .. tab-set ::
66+
67+ .. tab-item :: Linux/Mac
68+
69+ .. code-block :: bash
70+
71+ export ANSRV_GEO_LICENSE_SERVER=127.0.0.1
72+ export ANSRV_GEO_ENABLE_TRACE=0
73+ export ANSRV_GEO_LOG_LEVEL=2
74+
75+ .. tab-item :: Windows
76+
77+ .. code-block :: bash
78+
79+ SET ANSRV_GEO_LICENSE_SERVER=127.0.0.1
80+ SET ANSRV_GEO_ENABLE_TRACE=0
81+ SET ANSRV_GEO_LOG_LEVEL=2
82+
83+ .. tab-item :: Manual Geometry service launch
84+
85+ In this case, there is no prior environment variable definition needed. They can
86+ directly be passed to the Docker container itself.
87+
88+
89+ Geometry service launcher
90+ ^^^^^^^^^^^^^^^^^^^^^^^^^
91+
4092The Geometry service can be launched locally in two different ways:
4193
4294.. tab-set ::
4395
4496 .. tab-item :: Using PyGeometry launcher
4597
46- This method will directly launch for you the Geometry Service and it
98+ This method will directly launch for you the Geometry service and it
4799 will provide a ``Modeler `` object.
48100
49101 .. code :: python
@@ -52,17 +104,18 @@ The Geometry service can be launched locally in two different ways:
52104
53105 modeler = launch_modeler()
54106
55- The previous ``launch_modeler() `` method will launch the Geometry Service under the default
107+ The previous ``launch_modeler() `` method will launch the Geometry service under the default
56108 conditions. For more configurability, please use ``launch_local_modeler() ``.
57109
58- .. tab-item :: Manual Geometry Service launch
110+ .. tab-item :: Manual Geometry service launch
59111
60- This method will involve the user manually launching the Geometry Service. Afterwards, please
61- refer to the next section in order to understand how to connect to it from PyGeometry.
112+ This method will involve the user manually launching the Geometry service. Remember to pass
113+ in the different environment variables needed. Afterwards, please refer to the next section in
114+ order to understand how to connect to it from PyGeometry.
62115
63116 .. code :: bash
64117
65- docker run --name ans_geo -p 50051:50051 ghcr.io/pyansys/pygeometry :windows-latest
118+ docker run --name ans_geo -e LICENSE_SERVER= < LICENSE_SERVER > - p 50051:50051 ghcr.io/pyansys/geometry :windows-latest
66119
67120
68121 Connect to the Geometry service
0 commit comments