s1d3sw1ped/scratchbox
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 6 Wiki Activity

api/ui: Allow per-scratch TTL down to 1m
Format / gofmt (push) Successful in 13s
Details
CI / Build (push) Successful in 22s
Details
CI / Go Tests (push) Successful in 23s
Details
Format / gofmt (pull_request) Successful in 12s
Details
CI / Build (pull_request) Successful in 20s
Details
CI / Go Tests (pull_request) Successful in 20s
Details

Browse Source 
#4
This commit is contained in:
s1d3sw1ped_bot
2026-09-01 21:16:36 +00:00
parent 1d301d29b6
commit de465d6818
6 changed files with 439 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -1
View File
@@ -218,9 +218,10 @@ All configuration is YAML.
- If no unit is provided, value is interpreted as bytes
- Examples: `5MB`, `100MiB`, `1GiB`, `1048576`
- Default: `100MiB`
- `default_ttl`: expiration applied to new scratches.
- `default_ttl`: expiration applied to new scratches when `POST /api/scratch` omits `ttl`.
- Must be `> 0` and `<= 24h`
- Default: `15m`
- Optional per-scratch `ttl` is a Go duration from `1m` through `24h`. Multipart uploads use form field `ttl`; raw-body POSTs use query `ttl`. Invalid or out-of-range values return 400. Infinite TTL is not allowed.
- `raw_cache_max_size`: max total decompressed bytes cached in memory for `/api/raw` range requests.
- Supported units: `B`, `KB`, `MB`, `GB`, `KiB`, `MiB`, `GiB` (case-insensitive)
- Must be `> 0`