Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:37
From version 58.1
edited by Erik Bakker
on 2023/11/16 07:06
Change comment: There is no comment for this version
To version 60.1
edited by Carlijn Kokkeler
on 2023/11/20 15:08
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
... ... @@ -67,9 +67,9 @@
67 67  
68 68  Once you have done so, we press "Save" and switch back to the "Runtime volumes" tab.
69 69  
70 -{{info}}When configuring a network volume, the following information is relevant to know:
70 +{{warning}}When configuring a network volume, the following information is relevant to know:
71 71  * When you create a network volume to a folder that contains sub-folders, all sub-folders are shared automatically and can be accessed from the flow level
72 -* When dealing with multiple hosts, you must create a specific entry per host, as this follows the guiding security principles of the underlying infrastructure.{{/info}}
72 +* When dealing with multiple hosts, you must create a specific entry per host, as this follows the guiding security principles of the underlying infrastructure.{{/warning}}
73 73  
74 74  ==== 3.1.3 Link Volume ====
75 75  
... ... @@ -89,6 +89,10 @@
89 89  * In the case of using the Volume option in combination with a Machine volume, the external system with which you exchange data on-premise via a file-based method needs to be able to write or read the data from the volume (i.e., directory) you have configured. Should this be a problem, the Bind mount alternative discussed below should be considered.
90 90  * The Volume option and Machine volume combination can also be used for eMagiz-only information that needs to be persistable, such as archiving.
91 91  * In the case of using the Volume option in combination with a Network volume, the path to read and write from becomes what you define in the target field.
92 +* In case of mapping a volume on a windows host machine to another one on a windows docker runtime when writing the source/target paths, the following small adjustment is required:
93 +** In the source/target path:
94 +a. All “\” in the path should be written as “/”. Example: C:\Users\xxxx\tmp should be written as C:/Users/xxxx/tmp
95 +
92 92  {{/warning}}
93 93  
94 94  === 3.2 Bind mount ===