This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
storage_management [2021/08/31 14:48] yves |
storage_management [2022/02/11 19:22] yves |
||
---|---|---|---|
Line 11: | Line 11: | ||
PMA.core supports the following storage media: | PMA.core supports the following storage media: | ||
- | * local hard disk (think of you conventional C: and D: drives and partitions) | + | * local hard disk (think of you conventional ''C:'' and ''D:'' drives and partitions) |
- | * network storage like SMB shares (must be accessible via UNC \\server\path\to\data routes) | + | * network storage like SMB shares (must be accessible via UNC ''%%\\server\path\to\data%%'' routes) |
* S3-compliant cloud storage (Amazon AWS, Western Digital HGST, NetApp, Arvados, IBM...) | * S3-compliant cloud storage (Amazon AWS, Western Digital HGST, NetApp, Arvados, IBM...) | ||
* Microsoft Azure storage | * Microsoft Azure storage | ||
Line 23: | Line 23: | ||
This hybrid configuration model also means you can scale easily over time: you can start with a setup whereby your slides are mostly placed on a (big) local hard disk. After a while, you switch over to your organization's network storage. Even at a later stage, you can transparently migrate to S3-compliant cloud storage. When you have an external collaborator that temporarily wants to share their slide collection with you, you can ask them to setup an FTP server and patch a root-directory through to that one. | This hybrid configuration model also means you can scale easily over time: you can start with a setup whereby your slides are mostly placed on a (big) local hard disk. After a while, you switch over to your organization's network storage. Even at a later stage, you can transparently migrate to S3-compliant cloud storage. When you have an external collaborator that temporarily wants to share their slide collection with you, you can ask them to setup an FTP server and patch a root-directory through to that one. | ||
- | [[working_with_root_directories|Root-directory resources]] can have authentication and impersonation information attached to them. In addition, PMA.core has its own [[acl|access control lists]] to determine what [[groups]] and [[user-management|individual users]] can see and do (according to [[crud|the CRUD principle]]). | + | [[working_with_root_directories|Root-directory resources]] can have authentication and impersonation information attached to them. In addition, PMA.core has its own [[acl|access control lists]] to determine what [[groups]] and [[user_management|individual users]] can see and do (according to [[crud|the CRUD principle]]). |
A comprehensive blog article on the subject of storage and image management is provided at [[https://realdata.pathomation.com|our blog]]. | A comprehensive blog article on the subject of storage and image management is provided at [[https://realdata.pathomation.com|our blog]]. | ||