I am also interested in the potential for extensions to the Shotwell database.
Doing a dump of photo.db and importing into my db gets me started, but keeping mine up to date with changes to photo.db gets tricky. How about a Shotwell option which would maintain a persistent journal of changes to the db, it would simplify keeping my db in sync with photo.db. Thanks, Kent On Mon, Nov 21, 2011 at 2:33 PM, Jason Long <[email protected]> wrote: > I would like to use Postgres as a data source for Shotwell. > > I do not care about multiple users accessing the data. I want to use > shotwell to manage the photos locally. > > I will have a copy on a remote server via rsync that will match the photos > locally. > > I just want to use Shotwell to manage tags and events and have these > changes synced automatically to my server where I will run a custom photo > library viewer. I will probably rsync the thumbnails Shotwell creates as > well. > > Postgres can easily handle keeping the database in sync and I > can easily keep the images up to date with rsync. > > If this proves to be difficult I guess I will just dump the database in raw > SQL from SQLLite and run it into postgres remotely. > > Any ideas? > _______________________________________________ > Shotwell mailing list > [email protected] > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
