klevze/UploadShied
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rename project to UploadShield: update runtime, configs, docs, and provisioning; run lint/tests

Browse Source
This commit is contained in:
Gregor Klevže
2026-02-12 14:48:07 +01:00
parent d1310e0844
commit 7c8bccc911
20 changed files with 95 additions and 104 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
CONFIG_REFERENCE.md
View File

@@ -1,6 +1,6 @@
# Configuration Reference
This file maps the top-level configuration keys used by `upload-logger.json` (UploadShield) to their effect and defaults. Use absolute paths in production where possible.
This file maps the top-level configuration keys used by `uploadshield.json` (UploadShield) to their effect and defaults. Use absolute paths in production where possible.
## Top-level sections
@@ -48,7 +48,7 @@ This file maps the top-level configuration keys used by `upload-logger.json` (Up
- `allow_xml_eval` (bool) — relax `eval()` detection for XML/SVG content when true.
- `custom_patterns` (array) — array of PCRE patterns (as strings) applied to the file head. Invalid patterns are ignored.
## Example `upload-logger.json`
## Example `uploadshield.json`
```json
{
@@ -67,6 +67,6 @@ This file maps the top-level configuration keys used by `upload-logger.json` (Up
- Use absolute paths in `paths.*` when deploying under systemd/Ansible to avoid cwd surprises.
- Ensure `quarantine_dir` is inaccessible from the web and set to owner `root` and mode `0700`; files inside should be `0600`.
If you want, I can generate a per-site `upload-logger.json` filled with your preferred absolute paths and ownership values.
If you want, I can generate a per-site `uploadshield.json` filled with your preferred absolute paths and ownership values.
--