Changes for page Volume Mapping (On-premise)
Last modified by Erik Bakker on 2024/08/26 12:37
From version 68.1
edited by Erik Bakker
on 2024/03/05 08:56
on 2024/03/05 08:56
Change comment:
There is no comment for this version
To version 72.1
edited by Erik Bakker
on 2024/08/26 12:37
on 2024/08/26 12:37
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -14,8 +14,9 @@ 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 -* Volume17 +* Machine volume 18 18 * Bind mount 19 +* Network volume 19 19 * Temporary file system 20 20 * Named pipe 21 21 ... ... @@ -108,7 +108,7 @@ 108 108 109 109 === 3.3 Temporary file system === 110 110 111 -{{info}}This option is only relevant when running on Linux.{{/info}} 112 +{{info}}This option is only relevant when running on **Linux**.{{/info}} 112 112 113 113 The temporary file system option is for you if you do not want to work with **persistent** data but require **non-persistent** data. This way, you can increase the container's performance by avoiding writing into the container's writable layer. 114 114 ... ... @@ -123,7 +123,7 @@ 123 123 124 124 === 3.4 Named pipe === 125 125 126 -{{info}}This option is only relevant when running on Windows.{{/info}} 127 +{{info}}This option is only relevant when running on **Windows**.{{/info}} 127 127 128 128 A named pipe is a named, one-way or duplex pipe for communication between the pipe server and one or more pipe clients. All instances of a named pipe share the same pipe name, but each instance has its own buffers and handles, and provides a separate conduit for client/server communication. Any process can access named pipes, subject to security checks, making named pipes an easy form of communication between related or unrelated processes. 129 129 ... ... @@ -153,6 +153,8 @@ 153 153 154 154 == 5. Suggested Additional Readings == 155 155 156 -If you are interested in this topic and want more information, please read the help text provided by eMagiz. 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"]] 157 157 158 158 )))((({{toc/}}))){{/container}}{{/container}}