On 21 February 2012 09:05, Turgut Durduran <[email protected]> wrote: > > >>Instead of copying the entire db back and forth, why not just have it on a >>network drive like I do? NFS or SMB could be used. To make sure the DB is OK >>when starting shotwell you could create a little wrapper-script to check the >>db before executing shotwell. >> >>Having it in a Dropbox (or similar) folder would also work. >> >>(sorry for top-posting but this is how I must have my MTA configured @ work) >> >>Rgds//Thomas > > > Hi Thomas, > > > Dropbox would indeed work since it keeps copies of the files locally but a > network drive would not work for me since I work on my photos while > travelling often without an internet connection. I worry a bit about Dropbox > since sometimes I seem to end up in a very bandwidth consuming continuous > syncing when working on something interactively from there.
Note that you can pause syncing on Dropbox until you have finished edits, in order to prevent it repeatedly uploading a modified file. Also it can be set not to automatically start on boot so that you have to manually start it when you want to sync. Colin _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
