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/setup.rst
+35-13Lines changed: 35 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,23 +31,29 @@ Copy this file to your working directory, and update it to suit your needs.
31
31
32
32
cp examples/config/wis2box.env dev.env
33
33
34
-
.. note::
35
-
36
-
You must map ``WIS2BOX_HOST_DATADIR`` to the absolute path of a directory on your host machine. This path will be mapped to ``/data/wis2box`` inside the wis2box-management container
37
-
To enable external data sharing you must set ``WIS2BOX_URL`` to the URL pointing to where your host is exposed on the public network.
38
-
39
34
.. note::
40
35
Please ensure you set ``WIS2BOX_BROKER_PASSWORD`` and ``WIS2BOX_STORAGE_PASSWORD`` to your own unique values.
41
36
42
37
You will use these passwords to connect to your broker and MinIO storage to help you debug your wis2box services.
43
38
44
39
Do not share these passwords with external parties.
45
40
46
-
The next sections assume you use an environment variable for ``WIS2BOX_HOST_DATADIR`` that is set to same value used in ``dev.env``:
41
+
.. note::
42
+
43
+
You must map ``WIS2BOX_HOST_DATADIR`` to the absolute path of a directory on your host machine. This path will be mapped to ``/data/wis2box`` inside the **wis2box-management** container.
44
+
To enable external data sharing you must set ``WIS2BOX_URL`` to the URL pointing to where your host is exposed on the public network.
45
+
46
+
For example you can create a ``wis2box-data`` directory in your home directory as follows:
47
+
48
+
.. code-block:: bash
49
+
50
+
mkdir /home/<your-username>/wis2box-data
51
+
52
+
And you can edit ``dev.env`` to match the location
And edit ``${WIS2BOX_HOST_DATADIR}/metadata/station/station_list.csv`` to include the data for your stations.
172
+
And edit ``~/wis2box-data/metadata/station/station_list.csv`` to include the data for your stations.
167
173
168
174
.. note::
169
175
@@ -181,7 +187,13 @@ Discovery metadata records can be defined using the YAML syntax shared via ``WIS
181
187
182
188
An example is provided in ``surface-weather-observations.yml``. Each dataset requires its own discovery metadata configuration file.
183
189
184
-
You can copy the file ``surface-weather-observations.yml`` to the directory you defined for ``WIS2BOX_HOST_DATADIR`` and update it to provide the correct discovery metadata for your dataset:
190
+
You can copy the file ``surface-weather-observations.yml`` to the directory defined for ``WIS2BOX_HOST_DATADIR``:
And update it to provide the correct discovery metadata for your dataset:
185
197
186
198
* replace ``[country].[centre_id].data.core.weather.surface-based-observations.synop`` with the topic as previously used in ``$WIS2BOX_HOST_DATADIR/data-mappings.yml``
187
199
* text provided in ``identification.title`` and ``identification.abstract`` will be displayed in the wis2box user interface
@@ -205,6 +217,16 @@ This might take a while the first time, as Docker images will be downloaded.
205
217
The ``wis2box-ctl.py`` program is used as a convenience utility around a set of Docker Compose commands.
206
218
You can customize the ports exposed on your host by editing ``docker-compose.override.yml``.
207
219
220
+
.. note::
221
+
222
+
If you get the error:
223
+
224
+
``docker.errors.DockerException: Error while fetching server API version: ('Connection aborted.', PermissionError(13, 'Permission denied'))``
225
+
226
+
Please ensure your username is added to the docker group ``sudo usermod -aG docker <your-username>``.
227
+
Logout and log back in so that your group membership is re-evaluated.
228
+
229
+
208
230
Once the command above is completed, check that all services are running (and healthy).
0 commit comments