Comment 10 for bug 118700

You are right ;) But that does not leave me manually tweaking the database. It leaves me
 1. configuring NFS on either backend/frontend machine by hand and
 2. adding the exported directory as a Storage Group at the frontend machine
 3. taking care for a stable and performant network connection.

Due to the complexity of possible installation/mount scenarios this might be a thread for the "mythbuntu-control-centre" which is able/build to handle package management or other system configuration tasks - already containing nfs server under "system-services".

But that does not offer a unique procedure of (automatically) including different Storage Groups that are avaiable from other backends via NFS. However: the problem using different exported directories from different backends you (Mario) decribed above is now solved with "Storage Groups".

It might be a solution to add a mytharchive option "share (for backends) / use (for frontends) directories via fileserver" - and let the user choose between nfs/smbfs/cifs. The implementation of that task would be indeed not be a trivial one, but possible ;)

Automatically solve this task assumes that every user of mytharchive on a client with "only frontend installation" will need an configured file server on the backend. And - cross installation issues over system boarders will probably not be realistic ever. So this task will has to be done on the backend manually anyway - but could somehow be supported through mytharchive/control-centre.

Also not considered is the fact that some users might not know how network performance and stability issues can leave such a system nearly unusable (e.g. some might try a sloppy wireless connection).

To come to an end:
------------------------
For now there should be a warning message when using mytharchive on a "pure" frontend machine. Pointing to a help page how to configure a "networked" frontend/backend system the right way might be a good idea though.