enigma-bbs/docs/filebase/first-file-area.md

87 lines
3.2 KiB
Markdown
Raw Normal View History

---
layout: page
title: Configuring a File Base
---
2018-12-04 23:56:05 +00:00
## Configuring a File Base
ENiGMA½ offers a powerful and flexible file base. Configuration of file the file base and areas is handled via the `fileBase` section of `config.hjson`.
2018-12-04 23:56:05 +00:00
## ENiGMA½ File Base Key Concepts
First, there are some core concepts you should understand:
* Storage Tags
* Areas (and Area Tags)
2018-12-04 23:56:05 +00:00
### Storage Tags
*Storage Tags* define paths to physical (file) storage locations that are 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 (defaults to `/path/to/enigma-bbs/file_base`).
2018-12-04 23:56:05 +00:00
Below is an example defining some storage tags using the relative and fully qualified forms:
```hjson
storageTags: {
2018-12-04 23:56:05 +00:00
retro_pc_dos: "dos" // relative
retro_pc_bbs: "pc/bbs" // still relative!
bbs_stuff: "/path/to/bbs_stuff_storage" // fully qualified
}
```
2018-12-04 23:56:05 +00:00
:information_source: On their own, storage tags don't do anything — they are simply pointers to storage locations on your system.
2018-12-05 01:24:43 +00:00
:information_source: Remember that paths are case sensitive on most non-Windows systems!
### Areas
2018-12-04 23:56:05 +00:00
File base *Areas* are configured using the `fileBase::areas` configuration block in `config.hjson`. Valid members for an area are as follows:
2018-12-04 23:56:05 +00:00
| Item | Required | Description |
|--------|---------------|------------------|
| `name` | :+1: | Friendly area name. |
| `desc` | :-1: | Friendly area description. |
2018-12-04 23:58:21 +00:00
| `storageTags` | :+1: | An array of storage tags for physical storage backing of the files in this area. If uploads are enabled for this area, **first** storage tag location is utilized! |
2018-12-04 23:56:05 +00:00
| `sort` | :-1: | If present, provides the sort key for ordering. `name` is used otherwise. |
Example areas section:
```hjson
areas: {
retro_pc: {
name: Retro PC
desc: Oldschool PC/DOS
2018-12-04 23:56:05 +00:00
storageTags: [ "retro_pc_dos", "retro_pc_bbs" ]
}
}
```
2018-12-04 23:56:05 +00:00
The above example defines an area called "Retro PC" which is referenced via the *area tag* of `retro_pc`. Two storage tags are used: `retro_pc_dos`, and `retro_pc_bbs`. These storage tags can be seen in the Storage Tags example above.
## Example Configuration
2018-12-04 23:59:56 +00:00
This combines the two concepts described above. When viewing the file areas from ENiGMA½ a user will only see the "Retro PC" area, but the files in the area are stored in the two locations defined in the `storageTags` section. We also show a uploads area. Uploads are allowed due to the [ACS](acs.md) block. See [Uploads](uploads.md) for more information.
```hjson
fileBase: {
areaStoragePrefix: /enigma-bbs/file_base
storageTags: {
2018-12-04 23:56:05 +00:00
retro_pc_dos: "dos"
retro_pc_bbs: "pc/bbs"
}
areas: {
retro_pc: {
2018-04-29 15:13:16 +00:00
name: Retro PC
desc: Oldschool PC/DOS
2018-12-04 23:56:05 +00:00
storageTags: [ "retro_pc_dos", "retro_pc_bbs" ]
}
uploads: {
name: Uploads
desc: User uploads
acs: {
// allow any user to upload here
write: GM[users]
}
storageTags: [ "user_uploads" ]
2018-04-29 15:13:16 +00:00
}
}
}
```
## Importing Areas
Areas can also be imported using [oputil](/docs/admin/oputil.md) using proper FileGate "RAID" aka `FILEBONE.NA` style files. After importing areas, you may wish to tweak configuration such as better `desc` fields, ACS, or sorting.