mutil_file_toss
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
mutil_file_toss [2016/04/19 03:31] – avon | mutil_file_toss [2023/01/03 00:49] (current) – added ignore case avon | ||
---|---|---|---|
Line 63: | Line 63: | ||
allow_replace = true | allow_replace = true | ||
| | ||
+ | |||
+ | == Ignore Case == | ||
+ | |||
+ | If ' | ||
+ | |||
+ | ignore_case = true | ||
== Automatically Create New File Bases == | == Automatically Create New File Bases == | ||
Line 74: | Line 80: | ||
== Define Directory Prefix == | == Define Directory Prefix == | ||
- | The directory prefix for auto-created bases. | + | The directory prefix for auto-created |
- | ; | + | This will be used with the areatag appended onto it, so for example if prefix was set to dir_prefix=c: |
- | ; dir_prefix=c: | + | |
- | ; | + | |
- | ; And the areatag was " | + | dir_prefix = c: |
- | ; c: | + | |
- | ; | + | |
- | ; And the datafile would be fdn_nodelist | + | You then set a number of options as the **default values** MUTIL will apply when a file base is auto-created: |
+ | |||
+ | ; Display file to use | ||
+ | dispfile | ||
+ | ; Template to use | ||
+ | template | ||
+ | ; ACS to see the file base | ||
+ | acs_list | ||
+ | ; ACS to use FTP to access the file base | ||
+ | acs_ftp | ||
+ | ; ACS to download files in the file base | ||
+ | acs_download | ||
+ | ; ACS to upload files to the file base | ||
+ | acs_upload | ||
+ | ; ACS to hatch files from the file base to connected nodes | ||
+ | acs_hatch | ||
+ | ; ACS to use the file base with sysop access | ||
+ | acs_sysop | ||
+ | |||
+ | |||
+ | ; true/false type values 0=false 1=true (newscan 2=forced) | ||
+ | |||
+ | ; are downloads from this base ' | ||
+ | free_files | ||
+ | ; should Mystic display the uploader of files in this base? | ||
+ | show_uploader = 1 | ||
+ | ; should Mystic include files in this base as part of a 'new files' scan? | ||
+ | new_scan | ||
+ | |||
+ | |||
+ | == Define Specific Auto-Create Settings Based On Sender == | ||
+ | |||
+ | If you want to create settings specific to certain node addresses that send your system messages - you can! | ||
+ | |||
+ | For example, if you wanted to auto create bases that were linked to your fsxNet feed using the fsxNet HUB address of 21:1/100 , you have defined fsxNet as file group #1 in the File Group Editor, you want non-validated users (s10) to see files in the base, but only validated users (s20) to be able to download. You would set something like the following: | ||
+ | |||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | | ||
mutil_file_toss.txt · Last modified: 2023/01/03 00:49 by avon