nextcloud / nextcloud/server

Add support to custom user uploads dir

Open
#38,505 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement feature: dav hotspot: file transfer performance performance 🚀
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

Is your feature request related to a problem? Please describe.
Hi Team, I notice that actually is not possible customize the path where temporary uploads ,<user_id>/uploads, are stored. This happen for example with Chunk file.

It's possible customize the temp path for PHP and so on, but ufter tmp path, chunks go into <user_id>/uploads and then, after assebling, will go to the standar data folder for user.

It will be cool, have a settings that will allow us to "link" <user_id>/uploads to specific path, where we can mount, for example, local storage, that in general is much faster than long term storage.

Describe the solution you'd like
Add a option to customize <user_id>/uploads or adding a symlink to it.

Describe alternatives you've considered
Actually there is no alternative apart disable chunking.

Additional context
I will send you a PR that will address this feature with usage of symlink and adding of new config parameter called uploadsdirectory.
More info in the PR.

Thanks

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the chunk-upload handling and the <user_id>/uploads path described in the issue, then trace how the proposed uploadsdirectory setting would interact with the standard data folder. Check existing storage-related tests and add coverage showing that the temporary upload location can be configured or linked without breaking assembly.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.