89 lines
3.8 KiB
Markdown
89 lines
3.8 KiB
Markdown
# File Bases
|
|
Starting with version 0.0.4-alpha, ENiGMA½ has support for File Bases! Documentation below covers setup of file area(s), but first some information on what to expect:
|
|
|
|
## A Different Appoach
|
|
ENiGMA½ has strayed away from the old familure setup here and instead takes a more modern approach:
|
|
* [Gazelle](https://whatcd.github.io/Gazelle/) inspired system for searching & browsing files
|
|
* No File Conferences (just areas!)
|
|
* File Areas are still around but should generally be used less. Instead, files can have one or more tags. Think things like `dos.retro`, `pc.warez`, `games`, etc.
|
|
* Temporary web (http:// or https://) download links in additional to standard X/Y/Z protocol support
|
|
* Users can star rate files & search/filter by ratings
|
|
* Concept of user defined filters
|
|
|
|
## Other bells and whistles
|
|
* A given area can span one to many physical storage locations
|
|
* Upload processor can extract and use `FILE_ID.DIZ`/`DESC.SDI`, for standard descriptions as well as `README.TXT`, `*.NFO`, and so on for longer descriptions
|
|
* Upload processor also attempts release year estimation by scanning prementioned description file(s)
|
|
* Fast indexed Full Text Search (FTS)
|
|
* Duplicates validated by SHA-256
|
|
|
|
## Configuration
|
|
Like many things in ENiGMA½, configuration of file base(s) is handled via `config.hjson` -- specifically in the `fileBase` section.
|
|
|
|
```hjson
|
|
fileBase: {
|
|
areaStoragePrefix: /path/to/somewhere/
|
|
|
|
storageTags: {
|
|
/* ... */
|
|
}
|
|
|
|
areas: {
|
|
/* ... */
|
|
}
|
|
}
|
|
```
|
|
|
|
(Take a look at `core/config.js` for additional keys that may be overridden)
|
|
|
|
### Storage tags
|
|
**Storage Tags** define paths to a physical (file) storage location that can later be referenced in a file *Area* entry. Each entry may be either a fully qualified path or a relative path. Relative paths are relative to the value set by the `areaStoragePrefix` key. Below is an example defining a both a relative and fully qualified path each attached to a storage tag:
|
|
|
|
```hjson
|
|
storageTags: {
|
|
retro_pc: "retro_pc" // relative
|
|
retro_pc_bbs: "retro_pc/bbs" // still relative!
|
|
bbs_stuff: "/path/to/bbs_stuff_storage" // fully qualified
|
|
}
|
|
```
|
|
|
|
### Areas
|
|
File base **Areas** are configured using the `fileBase::areas` configuration block in `config.hjson`. Each entry within `areas` must contain a `name`, `desc`, and `storageTags`. Remember that in ENiGMA½ while areas are important, they should generally be used less than in tradditional BBS software. It is recommended to favor the use of more **tags** over more areas.
|
|
|
|
Example areas section:
|
|
```hjson
|
|
areas: {
|
|
retro_pc: {
|
|
name: Retro PC
|
|
desc: Oldschool PC/DOS
|
|
storageTags: [ "retro_pc", "retro_pc_bbs" ]
|
|
acs: {
|
|
write: GM[users] /* optional, see ACS below */
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
#### ACS
|
|
If no `acs` block is supplied, the following defaults apply to an area:
|
|
* `read` (list, download, etc.): `GM[users]`
|
|
* `write` (upload): `GM[sysops]`
|
|
|
|
To override read and/or write ACS, supply a valid `acs` member.
|
|
|
|
#### Uploads
|
|
Note that `storageTags` may contain *1:n* storage tag references. **Uploads in a particular area are stored in the first storage tag path**.
|
|
|
|
## Web Access
|
|
Temporary web HTTP(S) URLs can be used to download files using the built in web server. Temporary links expire after `fileBase::web::expireMinutes`. The full URL given to users is built using `contentServers::web::domain` and will default to HTTPS (http://) if enabled with a fallback to HTTP. The end result is users are given a temporary web link that may look something like this: `https://xibalba.l33t.codes:44512/f/h7JK`
|
|
|
|
See [Web Server](web_server.md) for more information.
|
|
|
|
## oputil
|
|
The `oputil.js` +op utilty `file-base` command has tools for managing file bases. For example, to import existing files found within **all** storage locations tied to an area:
|
|
|
|
```bash
|
|
oputil.js file-base --scan some_area
|
|
```
|
|
|
|
See `oputil.js file-base --help` for additional information. |