Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:37
From version 72.1
edited by Erik Bakker
on 2024/08/26 12:37
Change comment: There is no comment for this version
To version 69.1
edited by Erik Bakker
on 2024/03/05 08:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,9 +14,8 @@
14 14  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.
15 15  
16 16  There are several options for volume mapping for your on-premise machine.
17 -* Machine volume
17 +* Volume
18 18  * Bind mount
19 -* Network volume
20 20  * Temporary file system
21 21  * Named pipe
22 22  
... ... @@ -154,8 +154,6 @@
154 154  
155 155  == 5. Suggested Additional Readings ==
156 156  
157 -* [[Fundamentals (Menu)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
158 -** [[Current Generation (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]
159 -* [[Volume Mapping (Search Result)>>https://docs.emagiz.com/bin/view/Main/Search?text=%22volume%20mapping%22&f_type=DOCUMENT&f_space_facet=0%2FMain.&f_locale=en&f_locale=&f_locale=en&r=1||target="blank"]]
156 +If you are interested in this topic and want more information, please read the help text provided by eMagiz.
160 160  
161 161  )))((({{toc/}}))){{/container}}{{/container}}