| Summary | filesystem driver |
| Queue | Forwards |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | offermann (at) thielpark (dot) de |
| Created | 02/17/2005 (1179 days ago) |
| Due | |
| Updated | 11/28/2005 (895 days ago) |
| Assigned | |
| Resolved | 11/28/2005 (895 days ago) |
| Attachments | filesystem.zip ![]() |
| Milestone | |
| Patch |
State ⇒ Rejected
No feedback.State ⇒ Feedback
As the FTP driver already uses VFS (which also has a filesystem driver) to upload the .forward files, you should instead extend the existing driver to allow configuration of the VFS backend instead of hardcoding FTP usage.State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ filesystem driver
Queue ⇒ Forwards
New Attachment: filesystem.zip
I coded a new driver. It works directly on the filesystem. I included some configuration options to determine where the .forward-file should go, but it is probably not yet flexible enough to fit everyones needs. I'm open to suggestions. Obviously the webserver needs write access to the directory. I'm not very good with filesystem permissions, perhaps someone comes up with a better umask.