Yes I think the proposed design would work with local files also. There multiple ways to achieve this. option 1: add a new column in the database where you put "local", or "remote01".... option 2: is a dedicated mode for remote storage where every local database only works against one remote server.
I think option 2 is ideal, since you have a clean change of operation mode. One way to change active database is have a small menu, like you have in Google Chrome to change between active user/database man. 6. jul. 2020, 11:54 skrev Robert Bridge <rob...@robbieab.com>: > > > On Sun, 5 Jul 2020 at 19:26, Torstein Eide <torste...@gmail.com> wrote: > >> My first thoughts about architecture is the following: >> >> # Server: >> >> - Provides an API to the Client. >> - Is the only direct user of the database, so SQLite will still work, >> but Mysql/MariaDB is much faster. >> - Have a web interface for management. >> - User upload images via API or web interface- >> - Server is responsible for generating thumbnails. >> - Server is responsible for handling storage of images. >> >> >> # Client: >> >> - Access the server via API. >> - Downloads thumbnails for faster browsing. >> - Download to local cache any images for editing. >> - Client adds new files to local cache first, then uploads in the >> background to the server. Alla OwnCloud. >> >> Since I don't know all the inner workings of darktable there is >> probably internal service I have skipt. >> >> > Yay! Someone actually starting a proper specification! > > Question though: How would your proposed design work with local files? > Would it force everything to be uploaded to the central DB? > > Ideally, I would argue we need darktable to be able to handle multiple > databases, both local and remote, because the single most important factor > with any such redesign is we must not break the current workflows. > > I think the bike shed should be painted purple by the way. :) > > Cheers, > Robert. > > > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
