Better Manage Upload Data Paths

[crossan007]

As a ChurchCRM system administrator, I should have a consistent location for all artifacts uploaded by system users. This aids not only in traditional application installations, but is even more important when moving to containerized platforms with special considerations for persistent vs ephemeral data stores.

Currently, stateful data is limited to the MySQL database, uploaded images, application logs, and the configuration file; however, it is conceivable that additional file upload types become available. (#4658, #4510, #4498, #350)

This may be as simple as sequestering all user-supplied data to a path at <DocumentRoot>\Data, and adjusting all application logic to use the correct location.

[rsnyman]

Agreed. Also, making it configurable would also be helpful. For the Docker image in particular, the uploaded files would need to be stored outside of the document root.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 15 days with no activity.