On 04/29/2013 01:27 AM, John P Santos wrote:
Hi!
> I don't plan to have Darktable running from both machines at the same
> time. But even if I did, it would not be on the same film roll.
>
> But what you've said to me is interesting: How do I do the move of the
> files from within Darktable?
As far as I understand it, your main problem will result from the simple
fact that you want to move stuff to and fro automatically and, at the
moment at least, dt is quite "interactive", not much automation is
supported here AFAIK.
However, what you could probably consider is to use a temporary
library.db on your laptop and then just ingest the results to your final
database on your server system. It depends a bit on how your dt is set
up, there might be a problem with styles and presets. If you use them a
lot you'll stumble upon the problem that dt stores them in the image
database aka library.db. (IMHO the dt team should definitely reconsider
this point. I think it is no good idea to keep those in the same place
as the image data, as your usecase just points out very well.)
Anyway, if you don't use styles and presets, you could probably store
your library.db on /dev/shm (the ram disk, nicely gets droped if you
reboot the system, in case you reboot from time to time) and just ignore
it on your server as all your work gets stored to the sidecar files as
well. So all is recovered after syncing your working dir to the server
and ingest the images in dt. Unfortunately, there seems to be no
--ingest for darktable so you'd have to click through the ingestion
step, if you don't want to fiddle with the sqlite internals.
Another idea would be to try to just keep the path names the same on all
ends. AFAIK dt can handle missing image files without problems, at least
if you don't access them. So you might consider something like
/mnt/photo/...
which refers to different locations. Say a real dir on your notebook
that gets rsynced, a real dir on your server, a network share from the
server on your desktop... I'd not mount a network share inside of your
$HOME but as an external dir this worked very well for me in other
contexts.
Finally, Krogh describes an IMHO quite clever dir layout in his DAM book
[1]. Probably it's worth a look. He's not dealing with dt there, but
with some commercial apps that have basically the same problem with
database managed collections. Probably, this would give an idea as well.
[1] http://gso.gbv.de/DB=2.1/PPNSET?PPN=581078365
--
Kind regards, / War is Peace.
| Freedom is Slavery.
Alexander Wagner | Ignorance is Strength.
|
| Theory : G. Orwell, "1984"
/ In practice: USA, since 2001
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Darktable-users mailing list
Darktable-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-users
