feat(upload): bump per-file cap to 200MB end-to-end
Cluster: Appwrite container _APP_STORAGE_LIMIT 30000000 → 209715200 (200MB) in /root/services/appwrite/.env on kovaksoft-coolify, then docker compose up -d to roll the worker pool with the new value. Backup of the .env left at .env.bak.<date>. Bucket: job-files maximumFileSize updated to 209715200 via Appwrite MCP (storage_update_bucket). App: MAX_FILE_BYTES in both the upload API route and the original server action raised to 200MB. Client-side panel guard relaxed accordingly — one large file is now allowed to fill the entire batch (the 200MB proxy/serverActions cap is the bottleneck, not the per-file rule). Error copy updated. isletmem and any other tenants on the cluster also get the new limit, which is the desired behaviour — old 30MB ceiling was a relic of an Appwrite default that no DLS workflow can actually live with.
This commit is contained in:
@@ -20,7 +20,7 @@ import type {
|
||||
JobFileUploadState,
|
||||
} from "./job-file-types";
|
||||
|
||||
const MAX_FILE_BYTES = 30 * 1024 * 1024; // 30MB — bucket limit
|
||||
const MAX_FILE_BYTES = 200 * 1024 * 1024; // 200MB — bucket limit
|
||||
|
||||
function appwriteError(e: unknown, fallback = "Beklenmeyen bir hata oluştu."): string {
|
||||
if (e instanceof AppwriteException) return e.message || fallback;
|
||||
@@ -89,7 +89,7 @@ export async function uploadJobFilesAction(
|
||||
|
||||
for (const f of files) {
|
||||
if (f.size > MAX_FILE_BYTES) {
|
||||
return { ok: false, error: `${f.name} 30MB sınırını aşıyor.` };
|
||||
return { ok: false, error: `${f.name} 200MB sınırını aşıyor.` };
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user