Hooks can be used to automate the process of updating database columns
when new audio files are uploaded. A hook command reads the path of an
audio file and output a list of database columns to be updated with
their respective values. Currently, the only supported database tables
are calcms_events and calcms_audio_recordings. Some examples are
included
This commit adds a tool that removes all recordings that have been
played out in the past. The tool scans the database for recordings that
have a play time in the past and removes them from the system to free up
storage space and prevent outdated recordings from being played again.
This helps to ensure that only current and relevant recordings are
available for playback.
In the past Google Calendar exports were done by first removing all
events of a day and then create new ones. This takes a lot of time for
export and runs into Google Calendar usage limits after some time.
By now content will be compared before removing/creating a single event
one. To be able to do so, all other sync sources and targets have been
removed, so its only possible to export from database to Google Calendar
by this change.
To trigger an export you need to create a trigger file.
run_jobs.pl runs periodically e.g. started by cron and checks if a
trigger file exists and start sync_cms.pl to export the selected events
to the Google Calendar. Trigger files and jobs are configured at
jobs.config. Each job has a source and target file containing the access
data for calcms and the calendar.
Configuration files have been cleaned up. Old Accounts and passwords have
been removed. They hopefully should have been not active for a long time ;-)
