A file area contains a collection of files. You may create as many areas as you want and you may set different permissions for each area. File areas can also have subfolders (subdirectories) for more convenient management of large areas.
At a minimum a file area has an internal ID, name and storage location. The storage location is the root folder for directories and files stored in the area.
Some commands (such as the SendFile verb) allow you specify the path to a file. Where appropriate, these commands support a virtualized syntax that allows you to reference a file area (instead of an absolute path). Two virtual syntaxes are supported:
For example, suppose you have an area named GAMES and that GAMES has a file named MAZES.ZIP. You can marked the GAMES as area #2. Where supported (such as with SendFile), you can reference MAZES.ZIP using a virtualized syntax:
Note: If a file area name is a single letter (such as "D"), then the local path takes priority (that is, the path "D:\MAZES.ZIP" will be treated as a local file system path instead of a virtualized path. You can avoid this problem by using a file number or by renaming the file area to a different name containing at least two characters.
You can set the minimum permissions needed to list an area, download files from the area, and upload files to the area. All permissions are optional. If not defined, the BBS will use the default file area permissions defined in the system configuration file. It is recommended that you define the global permissions and then set file area permissions only when an exception is needed. This will reduce your maintenance overhead.
It is legal to allow a person to upload or download from an area without having permission to list files in the area. Some administrators like to redirect all file uploads to the same area; this makes it easier to audit and manage the uploads. Such a system typically allows users to upload files without having permission to list or download other files.
You can enable uploads, disable uploads, or redirect uploads to another file area. If you disable uploads, then no person (regardless of administrative rights) will be able to upload files to the area. This effectively makes the area read-only, which may be useful for sensitive or ROM-based areas. If you redirect uploads, then any uploaded files will be stored in a designated area.
At a minimum you will need to enter a name and storage location. The storage location will be created (if possible). You may need to manually create the storage location if the BBS software does not have sufficient permissions to create it.
The file area ID is a globally unique identifier (Guid) assigned by the BBS when the area is first created. You cannot change the ID because it is used by the engine to internally track information (such as the permissions assigned to the area). The ID is not the same as the file area number.
A text description; useful in menus.
Optionally defines a key name for the file area for your easier reference. The BBS engine does not use the assigned key name for any purpose except when you specify the key as a parameter to a script or function. Note that the Number setting (see above) has the same purpose as a key, except keys are easier to remember. Both can be removed or changed at any time.
The full name of the file area as it will appear to users.
The file area number is any number assigned by you for easier reference. The BBS engine does not use the assigned number for any purpose except when you specify the number as a parameter to a script or function. This means you can safely change a file area number as long as you also update any parameters. Note that you may want to use the human-friendly Key setting instead of a number.
A password that must be entered before the user can access the file area. A successful password entry does not override any other security permissions; it is an additional security measure on top of other measures.
A security expression that defines the permissions necessary to download files from the area.
A security expression that defines the permissions necessary to list files in the area.
A security expression that defines the permissions necessary to upload files to the area.