Changes for page Volume Mapping (On-premise)

Summary

• Page properties (2 modified, 0 added, 0 removed)

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,9 @@
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, the following small adjustment is required when writing the source/target paths:
	93	+** All “\” in the source/target path should be written as “/”. For example: C:\Users\xxxx\tmp should be written as C:/Users/xxxx/tmp.
	94	+
92	92	{{/warning}}
93	93
94	94	=== 3.2 Bind mount ===
...	...	@@ -103,6 +103,11 @@
103	103
104	104	{{info}}Note that when you use this option, your directory reference in your flow should refer to the "target" directory configured here.{{/info}}
105	105
	109	+{{warning}}
	110	+When configuring a bind mount on a windows host machine to another one on a windows docker runtime, the following small adjustment is required when writing the source/target paths:
	111	+**All “\” in the source/target path should be written as “/”. For example: C:\Users\xxxx\tmp should be written as C:/Users/xxxx/tmp.
	112	+{{/warning}}
	113	+
106	106	=== 3.3 Temporary file system ===
107	107
108	108	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.
...	...	@@ -113,12 +113,17 @@
113	113
114	114	[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage-filled-in.png]]
115	115
116		-{{warning}}We strongly advise you to define this number so that you can limit the potential impact this solution can have on the stability of your machine.{{/warning}}
	124	+{{warning}}
	125	+We strongly advise you to define this number so that you can limit the potential impact this solution can have on the stability of your machine. {{/warning}}
117	117
118	118	=== 3.4 Named pipe ===
119	119
120		-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.
	129	+*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.
121	121
	131	+{{warning}}
	132	+* When configuring a pipe path on a windows host machine to another one on a windows docker runtime, the following small adjustment is required when writing the source/target paths:
	133	+**All “\” in the source/target path should be written as “/”. For example: C:\Users\xxxx\tmp should be written as C:/Users/xxxx/tmp.{{/warning}}
	134	+
122	122	=== 3.5 Deployment consequences ===
123	123
124	124	{{warning}}