You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/user/getting-started.rst
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,20 +18,21 @@ When choosing the environment for the wis2box, consider the following:
18
18
19
19
.. important::
20
20
21
-
When using a wis2box instance as a WIS2 Node, it is **not recommended to use a host within your internal network**. Since a wis2box instance must be exposed to the public internet in order to operate as a WIS2 Node, it may introduce security risks to your internal network.
21
+
When using a wis2box instance as a WIS2 Node, it is **not recommended to use a host within your internal network**. Since a wis2box instance must be exposed to the public Internet in order to operate as a WIS2 Node, it is strongly recommended to decouple deployment from your internal network.
22
22
23
-
Please consider setting up your wis2box instance in the **cloud** or in another suitably isolated, internet-facing environment such as a **perimeter network (DMZ)** and setup a secure method to **push** data from your internal network to the wis2box instance.
23
+
Please consider setting up wis2box on cloud infrastructure or in another suitably isolated, Internet-facing environment such as a **perimeter network (DMZ)** and setup a secure method to **push** data from your internal network to the wis2box instance.
24
24
25
25
Before exposing the wis2box to the Internet, please review the 'security considerations' section in the :ref:`public-services-setup` section.
26
26
27
27
28
28
External resources used by wis2box
29
29
----------------------------------
30
30
31
-
Make sure that your wis2box-instance can access content from *GitHub*, *GitHub Container Registry*, and *Docker Hub*; to pull the required Docker images and updates.
32
-
To verify WIS2 compliance, the software will refer to standards defined on *iana.org* and *codes.wmo.int* which needs to be reachable from your wis2box instance at runtime.
31
+
Make sure that wis2box can access content from *GitHub*, *GitHub Container Registry*, and *Docker Hub*; to pull the required Docker images and updates.
33
32
34
-
The following domains must be reachable from your instance for the `wis2box-stack` to function correctly:
33
+
To verify WIS2 compliance, wis2box will use configurations, schemas and supporting files on *iana.org* and *codes.wmo.int* which needs to be reachable from the wis2box instance at runtime.
34
+
35
+
The following domains must be reachable from your instance for wis2box to function correctly:
0 commit comments