Moving the NFS mounts

Per a conversation with @barry, we’re going to move most NFS mounts on .org to a single centralized location. Here’s the checklist, in order:

  • Prepare PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. scripts to use the new locations if things are mounted (r9244-dotorg and a few others).
  • Set up the new location in nginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. for X-Accel-Redirect (r5733-deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors.).
  • Deploy the wporg-web role and reload nginx, which contains the new location in nginx.
  • Commit and deploy my patch (uploaded to SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at room), which adds new mounts to fstab-nfs and initializes the directories in a migrations script.
  • Run my script included in the patch as a global command to initialize the directories, add the new mounts to fstab, and mount them.

After that:

  • I then need to commit some new Nginx location blocks for the old URLs pointing to the new NFS locations (in some cases, they were directly accessible, such as The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. and some Rosetta stuff).
  • Those Nginx rules will then need to be deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors..
  • Remove and clean up after the old mounts once we verify everything works and nothing is using them. We’ll keep the uploads mount, but we’ll be able to remove everything else, including the BuddyPress and MU dl-archive mounts.