Tags
When defining access rights, you can also use tags (see :
Tags) to dynamically mount a directory depending on user account name for example (tags can be used in virtual and physical directory).
You can create : "c:\ftp\$DOM_NAME\$USR_ACCOUNT\" mounted in "/" with proper access rights.
When you login the server will search for your root directory in c:\ftp\ftp.gene6.com\anonymous\ (if you connect under anonymous on "ftp.gene6.com" domain)
Variations are possible, example : "c:\ftp\$USR_GROUP\" mounted in "/$USR_GROUP" to access files shared among the group.
Special mapping
Moving files in your ftp folder can make old direct links unavailable, users can not download files until the links are updated.
To solve this problem you can create mapping for files (just like a redirect in http, but transparently).
Let's take an example :
- you are distributing a setup file named with version number "setup_v1.0.0.exe" located in "c:\ftproot\www.yoursite.com\files\"
- a new version is released, so the file is now named "setup_v2.0.0.exe", all sites linking directly to your files need to update their download links (this can take some time ...)
The solution is to create a new access right like this :
virtual path : /files/setup_v1.0.0.exe
physical path : c:\ftproot\www.yoursite.com\files\setup_v2.0.0.exe
access rights : same as the original folder.
So when a user requests "setup_v1.0.0.exe", though the file does not exist anymore, it is served with content of "setup_v2.0.0.exe"
(limitation : the file is still named "setup_v1.0.0.exe" on user side unlike http where you can redirect to a new file).
This can also work if you move your files to another folder :
virtual path : /old_location/setup.exe
physical path : c:\ftproot\www.yoursite.com\new_location\setup.exe
access rights : same as the original folder.
The file will still be available and listed virtually in /old_location/ but it will only be physically present in \new_location\