Limits and settings¶
Settings¶
Under Settings → Object Storage:
| Setting | Default | What it does |
|---|---|---|
| Viewer Max Size (KB) | 1024 | The largest file the text viewer will open. |
| Image Preview Max Size (KB) | 8192 | The largest image the preview will open, and how much of an archive is read to list it. |
| Listing Page Size | 1000 | How many objects are asked for at a time while a folder loads. Stores return at most 1000. |
| Upload Part Size (MB) | 16 | Files larger than this are uploaded in parts of this size; smaller ones go in one request. |
The last two are read when a tab opens, so a change applies to tabs opened afterwards.
Each running upload holds one part in memory, so a larger part size means fewer requests and more memory per transfer — and several transfers run at once. The setting goes from 5 to 128 MB. An upload is limited to 10,000 parts; for a file too big to fit at the chosen size, Cleat uses larger parts by itself.
Limits¶
- Folder size. A single folder shows up to 200,000 entries. Past that, go into a sub-folder, or type a longer path into the path box.
- Preview. A file over its limit is not fetched at all. A tar or gzip archive over the limit is listed from its beginning and marked as partial; a zip over the limit cannot be listed, because its index is at the end of the file.
- Archive listings show the first 500 entries.
- One tab per connection. Opening a connection again brings its tab forward.
What reaches the log¶
Cleat's log records each request as an operation, a bucket and a key. It never records request headers, query strings, access keys or secret keys. As a second line of defence, the diagnostics bundle redacts AWS-format access key IDs and any labelled access-key, secret-key or signature value before it is written. Other providers' key IDs have no fixed format, so an unlabelled one cannot be recognised.