chore: add memoryLimit to CloudronManifest.json #7

Closed
opened 2026-11-04 16:21:46 +00:00 by wazolab · 0 comments
Owner

Context

The memoryLimit field is currently absent from CloudronManifest.json. Per the Cloudron manifest docs, the default is 256 MB when not specified.

Problem

256 MB is insufficient for Copyparty with the current feature set:

  • FFmpeg is installed and used for multimedia transcoding
  • e2dsa (filesystem indexing) and e2ts (multimedia indexing) are enabled in the default config
  • The SQLite index and thumbnail generation add memory pressure

The app will likely be OOM-killed silently during indexing on any non-trivial library.

Fix

Add to CloudronManifest.json:

"memoryLimit": 1073741824

This sets a 1 GB limit, which is reasonable for a file server with active FFmpeg + indexing. Can be tuned after real-world testing.

## Context The `memoryLimit` field is currently absent from `CloudronManifest.json`. Per the Cloudron manifest docs, the **default is 256 MB** when not specified. ## Problem 256 MB is insufficient for Copyparty with the current feature set: - FFmpeg is installed and used for multimedia transcoding - `e2dsa` (filesystem indexing) and `e2ts` (multimedia indexing) are enabled in the default config - The SQLite index and thumbnail generation add memory pressure The app will likely be OOM-killed silently during indexing on any non-trivial library. ## Fix Add to `CloudronManifest.json`: ```json "memoryLimit": 1073741824 ``` This sets a 1 GB limit, which is reasonable for a file server with active FFmpeg + indexing. Can be tuned after real-world testing.
wazolab self-assigned this 2026-11-04 16:21:46 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
wazolab/cloudron-copyparty#7
No description provided.