Yes, let’s do that, your friend’s server scenario does also match the intention of my proposals nicely. (Should be nicely covered, let me try to explain.)
Let’s consider that freedombox should be a good basis to organize photos (i.e. Zoph), but also much more. There are many apps, most need storage space (and for example with redundancy possibly). So it’s good not to only look for a Zoph solution, because having a more general solution has many more benefits.
With a couple of apps, Zoph being an example, the main data access may clearly not happen through direct file access. Nevertheless following the same conventions for data storage still allows them to play well with other apps, out of the box, for example with backup or sync apps, or your favorite contributed helper script. And all this without requiring every admin to sort out and configure a local solution, and possibly having to support many different custom solutions.
So, bulk storage is needed by multiple apps, and I’d rather not want to have to configure this for every app, and friend’s home server, separately. That would bring unnecessary problems.
As the default filesystem with freedombox is BTRFS, one solution is attaching additional disk(s) and to move the whole system over while running. (Recommended for sdcard based systems.)
With a central data storage convention for freedombox, one can also simply add an external storage (filesystem) and have it mounted. For example even at its base (
/home according to the proposal), and thus have all data (and configration) now residing on the (large) external disk. (Perfect for a fast SSD system with large storage disks.)
Note that additional disks (space or redundancy) may be added to the root- or home-filesystem as desired (with the default btrfs), completely independent from the /home directory conventions. The files would always be at the same predictable directory locations on every freedombox, regardless of the underlying disks, filesystem, network protocol, etc.
With freedombox (plinth) showing the free space of the filesystems (possibly warning if running low or running on sdcard), and plinth allowing to manage the disks, there should be no need for users to ever having to solve app specific file/directory selection problems.
(And I have left out the collaboration permission, network access, and backup and syncing possibilities (and left all those solved problems aside). But I think they are also truly practical for freedombox to really completely work out of the box, and mostly all based on following the useful and flexible multi-user
/home storage conventions.)