moon
/
enigma-bbs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Improve ACS & uploads docs around FB

This commit is contained in:
Bryan Ashby 2018-11-27 23:22:09 -07:00
parent 965c7b9ed1
commit e1862e6916
2 changed files with 30 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/filebase/acs.md
View File

@ -3,9 +3,10 @@ layout: page
title: ACS title: ACS
--- ---
## File Base ACS ## File Base ACS
[ACS Codes](/docs/configuration/acs.md) may be used to control acess to File Base areas by specifying an `acs` string in a file area's definition. If no `acs` is supplied in a file area definition, the following defaults apply to an area: [ACS Codes](/docs/configuration/acs.md) may be used to control access to File Base areas by specifying an `acs` string in a file area's definition. If no `acs` is supplied in a file area definition, the following defaults apply to an area:
* `read` (list, download, etc.): `GM[users]` * `read` : `GM[users]`: List/view the area and it's contents.
* `write` (upload): `GM[sysops]` * `write` : `GM[sysops]`: Upload.
* `download` : `GM[users]`: Download.
To override read and/or write ACS, supply a valid `acs` member. To override read and/or write ACS, supply a valid `acs` member.
@ -18,8 +19,13 @@ areas: {
desc: Oldschool PC/DOS desc: Oldschool PC/DOS
storageTags: [ "retro_pc", "retro_pc_bbs" ] storageTags: [ "retro_pc", "retro_pc_bbs" ]
acs: { acs: {
write: GM[users] // only users of the "l33t" group or those who have
// uploaded 10+ files can download from here...
download: GM[l33t]|UP10
} }
} }
} }
``` ```
## See Also
[Access Condition System (ACS)](/docs/configuration/acs.md)

21
docs/filebase/uploads.md
View File

@ -2,7 +2,24 @@
layout: page layout: page
title: Uploads title: Uploads
--- ---
## Uploads
The default ACS for file areas areas in ENiGMA½ is to allow read (viewing of the area), and downloads for users while only permitting SysOps to write (upload). See [File Base ACS](acs.md) for more information.
Note that `storageTags` may contain *1:n* storage tag references. To allow uploads to a particular area, change the ACS level for `write`. For example:
```hjson
uploads: {
name: Uploads
desc: User Uploads
storageTags: [
"uploads"
]
acs: {
write: GM[users]
}
}
````
:information_source: Remember that uploads in a particular area are stored **using the first storage tag defined in that area.**
:information_source: Any ACS checks are allowed. See [ACS](/docs/acs.md)
**Uploads in a particular area are stored in the first storage tag defined in an area.**