Use different Volumes for storage

I came with a situation that I consistently do in my WP installations, for example

Adding one or 2 volumes for WP uploads folder and change MySQL db to another volume.

RAID, network block storage, and other devices can offer redundancy and other desirable features. But when you are in a low budget situation or different infrastructure situation you would always prefer to increase Storage

In what situation would you need this:
- Databases grow over time, sometimes outgrowing the space on the file system.
- You can also run into I/O contention when they’re located on the same partition as the rest of the operating system.
- Volumes/Pods are cheaper

The idea in general would be that in the creation of a site, you could add a different storage path.

like:

`ee site create cdn.mywp.io --type=wp --uploadspath=/mnt/volume-uploads/ --dbpath=/mnt/volume-mysql/mysql-data/ --le --cache
`

`uploadspath` should change in the `wp_options`

`upload_path`
`upload_url_path`

or just define the upload path to wp-config.php

`define( 'UPLOADS', '/mnt/volume-uploads/' );`

I suppose that docker will do the correct changes inside the container for the storage location of `/mysql/` and the logs

Also if there are better ways to achieve this hope somebody could give insights.

Inizia dal punto di ingresso `ee site create` e verifica come vengono attualmente gestiti le impostazioni di upload di WordPress, lo storage MySQL, i volumi Docker e i log. L’issue non indica file o test; per considerarla completata sarebbe necessario definire e testare un modo per configurare percorsi separati per gli upload e il database durante la creazione del sito.

Scritto dal modello di indicizzazione a partire dal testo della issue.