http://autoindex.sourceforge.net/
Well, it served exactly our needs.
How I did it in short- create a new folder /var/www/recordings (debian).
Extract there the contents of autoindex files.
Make a symlink to your recordings FTP directory, in our case it's /home/ftp/cron/RECORDINGS.
ln -s /home/ftp/cron/RECORDINGS/ /var/www/recordings/RECORDINGS
chown -R -h www-data:www-data /var/www/recordings
To be able to use admin.php page and lead search with link to each recording, I created a second symlink
ln -s /home/ftp/cron/RECORDINGS/ /var/www/RECORDINGS
astguiclient.conf
- Code: Select all
....
# FTP recording archive connection information
VARFTP_host => 10.17.17.4
VARFTP_user => cron
VARFTP_pass => mypassword
VARFTP_port => 21
VARFTP_dir => RECORDINGS
VARHTTP_path => http://our.web.site/RECORDINGS
...
Indexes are disabled in apache2.conf:
- Code: Select all
...
DocumentRoot /var/www/
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory /var/www/>
Options -Indexes FollowSymLinks MultiViews
AllowOverride AuthConfig Indexes Options
Order allow,deny
Allow from all
# This directive allows us to have apache2's default start page
# in /apache2-default/, but still have / go to the right place
RedirectMatch ^/$ /apache2-default/
</Directory>
....
Set the appropriate permissions for the sensitive files.
When setting up AutoIndex put ./RECORDINGS/ for Base Directory.
The same way was for /var/www/reports, all our reports are copied daily to /home/ftp/cron/REPORTS.
Hope this helps for anyone with similar to our needs.
