[wp-trac] [WordPress Trac] #49440: Allow configuring the upgrade directory

WordPress Trac noreply at wordpress.org
Fri Feb 14 19:23:53 UTC 2020

#49440: Allow configuring the upgrade directory
 Reporter:  natesymer                    |      Owner:  (none)
     Type:  feature request              |     Status:  new
 Priority:  normal                       |  Milestone:  Awaiting Review
Component:  Upgrade/Install              |    Version:
 Severity:  normal                       |   Keywords:
  Focuses:  administration, performance  |
 `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.

Ticket URL: <https://core.trac.wordpress.org/ticket/49440>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list