Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:37
From version 65.1
edited by Erik Bakker
on 2023/11/26 20:34
Change comment: There is no comment for this version
To version 63.1
edited by Carlijn Kokkeler
on 2023/11/20 15:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -16,7 +16,7 @@
16 16  
17 17  This microlearning centers around learning how to correctly set up your volume mapping so you can exchange file-based data on-premise.
18 18  
19 -By volume mapping, we mean Creating a configuration through which the docker container can read and write data on a specific path on an on-premise machine. Note that the data can also be stored inside the docker container when (1) the other party writing or reading the data can access this path or (2) when the data is only relevant within the context of eMagiz.
19 +By volume mapping, we mean Creating a configuration through which the docker container can read and write data on a specific path on an on-premise machine. Note that the data can also be stored inside the docker container when the other party writing or reading the data can access this path or when the data is only relevant within the context of eMagiz.
20 20  
21 21  There are several options for volume mapping for your on-premise machine.
22 22  * Volume
... ... @@ -35,7 +35,7 @@
35 35  * Temporary file system
36 36  * Named pipe
37 37  
38 -Below, we will explain the differences between the various options available for your volume mapping. But before we do this, we explain how to set up this configuration within eMagiz. Then, you must navigate to Deploy -> Architecture on the model level. This overview lets you access the Volume mapping per runtime deployed on-premise. To do so, you can right-click on the runtime to access the context menu.
38 +Below, we will explain the differences between the various options available for your volume mapping. But before we do, we explain how to set up this configuration within eMagiz. Then, you must navigate to Deploy -> Architecture on the model level. This overview lets you access the Volume mapping per runtime deployed on-premise. To do so, you can right-click on the runtime to access the context menu.
39 39  
40 40  [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--volume-option-context-menu.png]]
41 41  
... ... @@ -108,7 +108,7 @@
108 108  
109 109  {{warning}}
110 110  When configuring a bind mount on a windows host machine to another one on a windows docker runtime, the following small adjustment is required when writing the source/target paths:
111 -** All “\” in the source/target path should be written as “/”. For example: C:\Users\xxxx\tmp should be written as C:/Users/xxxx/tmp.
111 +**All “\” in the source/target path should be written as “/”. For example: C:\Users\xxxx\tmp should be written as C:/Users/xxxx/tmp.
112 112  {{/warning}}
113 113  
114 114  === 3.3 Temporary file system ===