Transmission package does this web UI without need for PHP or special http server. busyboc_httpd does the job.
Features
* batch multiprocessing (eg. 10 torrents simultaneously with nice priority)
* automatic seeding when torrent finishes (configurable)
* configurable ports
* WWW interface transmission.cgi can be public (no password) as there is no delete provided.
* Accelerator keys (ALT-key) for CGI interface. See help for underlined keys.
* Per torrent and cumulative status
* start/stop/push and other commands avalable in WWW interface
* lightweight - low memory footprint
* tracker scrape info. Suggest best seed torrent from target dir.
* watchdog for auto restart/queue processing with cron
* syslog watchdog events
* mail notify when torrent finishes
* no state database required. Directory tree is database (slow, but failsafe)
* stable and portable. Deloped on Asus WL-500g Deluxe

Workflow

For queue torrent file processing there should exist tree directories:
source User should copy .torrent files here
work Used for torrent processing
target Place where finished torrents are put.

Typical file flow is source -> work -> target For every torrent file from source, directory with the same name is created. Then torrent file is moved into this directory and transmissiond is run in background and constantly supervised with transmission_watchdog.


The next clickable image shows how CGI interface looks like:


This figure shows transfer logs and command buttons for CGI interface: