Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:37
From version 70.1
edited by Erik Bakker
on 2024/03/05 13:03
Change comment: There is no comment for this version
To version 67.1
edited by Erik Bakker
on 2024/02/20 16:50
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  
... ... @@ -109,8 +109,6 @@
109 109  
110 110  === 3.3 Temporary file system ===
111 111  
112 -{{info}}This option is only relevant when running on **Linux**.{{/info}}
113 -
114 114  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.
115 115  
116 116  [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage.png]]
... ... @@ -124,10 +124,6 @@
124 124  
125 125  === 3.4 Named pipe ===
126 126  
127 -{{info}}This option is only relevant when running on **Windows**.{{/info}}
128 -
129 -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.
130 -
131 131  *The named pipe option can be selected, but we yet have to see a valid use case within the context of eMagiz for using this option. Therefore, we won't discuss this option further in this microlearning.
132 132  
133 133  {{warning}}