User Tools

Site Tools


rootdir_config

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
rootdir_config [2022/02/11 18:56]
yves [Adding mounting points]
rootdir_config [2022/09/15 19:54]
yves [Adding mounting points]
Line 40: Line 40:
 ==== Adding mounting points ==== ==== Adding mounting points ====
  
-PMA.core supports ​+PMA.core ​[[storage_management|supports ​different types of storage]] (see also [[https://​www.prweb.com/​releases/​pathomation_announces_support_for_cloud_storage_and_file_transfer_protocol_ftp_servers/​prweb18296771.htm|our press release]]):​ 
 ^ storage type ^ information needed ^ ^ storage type ^ information needed ^
-| local hard disk | a path reference like c:​\my_slides or e:​\department\pathology\staff\dr_seuss. Note that you cannot map network drives (drive letters like Y: or Z: are usually network drives) as root directories this way. | +| local hard disk | a path reference like ''​c:​\my_slides'' ​or ''​e:​\department\pathology\staff\dr_seuss''​. Note that you cannot map network drives (drive letters like Y: or Z: are usually network drives) as root directories this way. | 
-| network drives | a UNC path reference like \\server\sharename\our_slides. | +| network drives | a UNC path reference like ''​%%\\server\sharename\our_slides%%''​ ([[accessing_data_on_a_network|more about networks]]). | 
-| S3 storage | Access and secret key combination,​ a path to a bucket like /my_bucket. Sub-paths underneath this path are allowed, too. | +| [[rootdir_s3|S3 storage]] | Access and secret key combination,​ a path to a bucket like /my_bucket. Sub-paths underneath this path are allowed, too. | 
-| Azure storage | A connection string, container name. As of [[what_s_new_in_version_2.0.1|PMA.core 2.0.1]], you can also specify a path to traverse directly down a hierarchy within the container |+| [[rootdir_azure|Azure storage]] | A connection string, container name. As of [[what_s_new_in_version_2.0.1|PMA.core 2.0.1]], you can also specify a path to traverse directly down a hierarchy within the container |
 | FTP server | FTP server URL, username and password, optionally an initial path | | FTP server | FTP server URL, username and password, optionally an initial path |
  
 For some of these storage types, you'll also see a field "Chunk size". This has to do with [[caching]] and can almost always be left to its default setting. For some of these storage types, you'll also see a field "Chunk size". This has to do with [[caching]] and can almost always be left to its default setting.
  
-=== A note about (mapped) network drives === +In our [[rootdir_security|section ​on security]], [[rootdir_security#​accessing_secured_content|we elaborate more]] on each storage type.
- +
-In many organizations,​ it is commmon to map network paths to a drive letter. It's easier to remember that all the images are stored ​on the shared I: driverather than in the \\server_emea_48F\content\shared\incoming_slide_data\. PMA.core needs the latter path however to be able to mount content, rather than the I: drive letter. You cannot use the I: drive letter as a reference when attaching a new mounting point to a root directory. +
- +
-The reason for this is that your I: drive letter is a transient designation that only exists when you're logged in. In a server content (PMA.core is a server application running on [[https://​www.iis.net|Microsoft IIS server]]), the software runs unattended (i.e. without a human being logged ​on to the machine). The drive letter therefore is not available (in unattended mode), but the network path is.+
  
-Think of root directories then as PMA.core'​s own alternative to mapped network drive letters on your local computer. 
  
 ==== Nested references ==== ==== Nested references ====
rootdir_config.txt · Last modified: 2022/10/07 10:16 by yves