Changes for page Volume Mapping (On-premise)
Last modified by Erik Bakker on 2024/08/26 12:37
From version 56.1
edited by Erik Bakker
on 2023/04/11 12:39
on 2023/04/11 12:39
Change comment:
There is no comment for this version
To version 57.1
edited by Eva Torken
on 2023/06/20 17:02
on 2023/06/20 17:02
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e bakker1 +XWiki.etorken - Content
-
... ... @@ -113,13 +113,8 @@ 113 113 114 114 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. 115 115 116 -== 4. Assignment ==116 +== 4. Key takeaways == 117 117 118 -Navigate to Deploy -> Architecture and look at the Volume mapping options, read the help texts, and play around with the settings (if it is not a customer environment). 119 -This assignment can be completed with the help of the (Academy) project you created/used in the previous assignment. 120 - 121 -== 5. Key takeaways == 122 - 123 123 * File-based communication on-premise changes in the new runtime architecture 124 124 * There are two ways to store **persistent** data 125 125 ** Volume ... ... @@ -127,14 +127,9 @@ 127 127 * The Volume option is considered the best alternative because they have better performance, and bind mounts are dependent on the directory structure and OS of the host machine 128 128 * When you want to deal with **non-persistent** data, the Temporary file storage option is the way to go. 129 129 130 -== 6. Suggested Additional Readings ==125 +== 5. Suggested Additional Readings == 131 131 132 132 If you are interested in this topic and want more information, please read the help text provided by eMagiz. 133 133 134 -== 7. Silent demonstration video == 135 135 136 -This video demonstrates how you could have handled the assignment and gives context to what you have just learned. 137 - 138 -TBA 139 - 140 140 )))((({{toc/}}))){{/container}}{{/container}}