Differences

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

--- rootdir [2022/02/07 15:01]
yves
+++ rootdir [2022/03/14 14:15]
yves [Integrity check]
@@ Line 33: / Line 33: @@
 {{ :work.png?nolink&400 |}}
-The next section takes you through the different steps that you can take to configure root directories and mounting points. We also talk about the security precautions that you can take when configuring these.
+==== Configuration ====
-==== Start hosting your slides ====
+We have a [[rootdir_config|separate section]] in this wiki that takes you through the different steps that you can take to [[rootdir_config|configure root directories and mounting points]].
-This section allows the addition of new directories as well as the editing and deletion of existing ones.
+Root-directories can be labeled public or private, which allow you to [[rootdir_security#public_vs_private|take security precautions when configuring these]].
+==== Security ====
-The path of a directory must be an absolute path accessible by the host computer. Should the path not exist, an error message is shown:
+Root directories can be either [[rootdir_security#public_vs_private|public or private]].
-{{ :work2.png?nolink&400 |}}
+Who's accessed what (either public or private) folder can be monitored via the Access log tab.
-You can edit already existing root directories by clicking on the pencil behind each entry in the overview table:
+{{ ::access_log.png?nolink&400 |}}
-{{ :work3.png?nolink&400 |}}
+==== Logging ====
-Similarly, you may delete root directories by clicking on the delete icon behind each entry. A confirmation prompt at this point will give you one last chance to reconsider:
+Apart from manipulating root directories, monitoring their use is an important aspect of our software as well.
-{{ :work4.png?nolink&400 |}}
+You can monitor logs for several kinds of acivity:
+{{ :rootdir_logs.png?direct&400 |}}
+=== Audit trail ===
+The audit trail tab conbines any operations that were performed on both root directory entries and underlaying mounting point entries.
+{{ :rootdir_audit.png?direct&400 |}}
+The presented information [[21_cfr_part_11|21 CFR pârt 11 compliant]].
+=== Activity log ===
+In addition to an audit trail, an activity log is available that chronologically tell you which user has been accessing what slides in the root directory:
+{{ :rootdir_activity.png?direct&400 |}}
+=== Elmah log ===
+[[https://elmah.github.io/|Elmah error logs]] are a standard way of capturing runtime errors in software. While these logs are not specific to root directories, they can help troubleshoot intermittent problems. Examples include:
+  * connection information is (temporarily) no longer correct
+  * a file format may have been modified by its vendor and now no longer renders correctly
+{{ ::rootdir_elmah.png?direct&400 |}}
+==== Integrity check ====
+When problems persist over time, a structured and proactive approach is warranted.
+When you suspect certain slides in a particular root directory are corrupt, you can run an integrity check on a particular folder:
+{{ :rootdir_integrity.png?direct&400 |}}
+This attempts to read all slides in a folder and reports on the ones that fail. You should then [[format_troubleshoot|try to find out why such slides cannot be read]].
+For problems that only occur occasionally and don't appear to be persistent, [[elmah|Elmah logs]] are available to assist in for ad-hoc troubleshooting.

PMA.core 3

User Tools

Site Tools

Differences

Page Tools