Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:37
From version 67.1
edited by Erik Bakker
on 2024/02/20 16:50
Change comment: There is no comment for this version
To version 71.1
edited by Carlijn Kokkeler
on 2024/08/21 16:18
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
... ... @@ -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 -* Volume
17 +* Machine volume
18 18  * Bind mount
19 +* Network volume
19 19  * Temporary file system
20 20  * Named pipe
21 21  
... ... @@ -108,6 +108,8 @@
108 108  
109 109  === 3.3 Temporary file system ===
110 110  
112 +{{info}}This option is only relevant when running on **Linux**.{{/info}}
113 +
111 111  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.
112 112  
113 113  [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage.png]]
... ... @@ -121,6 +121,10 @@
121 121  
122 122  === 3.4 Named pipe ===
123 123  
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 +
124 124  *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.
125 125  
126 126  {{warning}}
... ... @@ -147,6 +147,11 @@
147 147  
148 148  == 5. Suggested Additional Readings ==
149 149  
150 -If you are interested in this topic and want more information, please read the help text provided by eMagiz.
157 +* [[Use Cases (Menu)>>doc:Main.eMagiz Academy.Use Cases.WebHome||target="blank"]]
158 +** [[File based Connectivity (Navigation)>>doc:Main.eMagiz Academy.Use Cases.File based Connectivity.WebHome||target="blank"]]
159 +* [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
160 +** [[File based Connectivity (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.File based connectivity.WebHome||target="blank"]]
161 +* [[Advanced (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]]
162 +** [[File based Connectivity (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.File based connectivity.WebHome||target="blank"]]
151 151  
152 152  )))((({{toc/}}))){{/container}}{{/container}}