WordPress.org

Make WordPress Core

Opened 8 weeks ago

#49440 new feature request

Allow configuring the upgrade directory

Reported by: natesymer Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Upgrade/Install Keywords:
Focuses: administration, performance Cc:

Description

wp-content/upgrade is not application code, and it's not data. WordPress shouldn't hardcode where this directory is (especially to a location under the webroot).

Instead, the upgrade directory should be user-configurable & transient. This would allow things to continue as they are - but if someone wants to host their WordPress on a slow disk (HDD, NFS), they could.

The problem is when you have a slow disk, updates can fail because of HTTP timeouts. For example, an NFS volume containing a wordpress install is mounted in the webroot. Moving files across a network to unzip them is insane! It would make so much more sense to use a location like /tmp, which is already optimized for such a use case as unzipping files. Often, /tmp is a tempfs, which actually lives in memory.

Change History (0)

Note: See TracTickets for help on using tickets.