Your Webcampak will probably have to store a (very) large number of pictures. It has been designed for this task and multiple features are available to manage and secure those files.
Hardware failure or human error (i.e. delete pictures by mistake) do happen, taking preventing actions is always preferable.
Webcampak is able to send pictures to a remote FTP server, users can also store pictures automatically on another source of the same Webcampak to prevent human errors (just keep in mind it will require twice the amount of disk space).
Webcampak is equipped with automated deletion mechanisms to ensure its internal hard disk never runs out of space. Those mechanisms can be configured to fit various requirements.
Even if Webcampak stores pictures to a remote server, it can use its internal disk space as a buffer to ensure no pictures are lost in case of network issue. Depending on the capture frequency and picture size, this buffer size can span days, even months.
In most cases, access to Webcampak files is done through FTP, using provisioned accounts.
A global FTP account (wpresources) is available for admins to access shared Webcampak elements, such as:
- cache files (temporary files created by Webcampak)
- Webcampak database (users, permissions, sources details)
- emails (queued, sent, failed)
- configuration files
- common watermark files (shared between all sources)
- xfer (queued, completed, failed)
Each source then gets its own FTP account giving access to its own directory tree, containing:
- live: directory containing hotlink pictures and videos
- pictures: directory containing pictures archives, with one sub-directory per capture day
- resources: directory containing various source-specific elements necessary for processing and source operation
- tmp: temporary directory used in processing and/or picture acquisition
- videos: directory containing generated videos