I've recently been playing with some of these issues as a result of an
upgrade to Kubuntu20. If you are talking about seeing them as a
removable collection, you could add them to your current default setup,
but this might involved re-initializing the database, which for 130MB
(just?) might take a while. At least for me, it could be that this is
because I store the metadata in the JPG, and not in a sidecar file
I believe you can also trick digikam in starting up with a different
~/.config/digikamrc file, e.g. I believe this works:
digikam --database-directory /photos/db --config /photos/db/digikamrc
but even in that case the identifier in the AlbumRoots would need to be
adjusted, and perhaps the specificPath as well, but then you should be
able to be "up" right away.
I didn't like this idea, since I would want all of the pictures in the
same database.
I am still in the middle of this upgrade, and as I posted in another
message, my trickery defeated me trying to say what's a removable and
what's a local collection.
If you look in the Collection Settings, there is also a Network Shares
option.
On 5/23/20 9:36 AM, Tonio Kroeger wrote:
> Hi all,
>
> I am accessing my photo collection from different machines. Currently
> I do this by "ssh -X". It is working, even via WLAN it is okay. My
> main issue is that the remote machine is a laptop and sometimes is
> shutdown or suspended and I have no chance to get informed before.
>
> Now I setup my raspberrypi 4 as a nfs-server and for accessing the
> pictures it is fine. So I am tempted to also copy the digikam-sqllite
> database on this nfs-share. Now I learned from the doku that this is
> highly discouraged. SQLlite does not load the database into main
> memory? In my case just 131MB? Is there an alternate idea for my
> setting? I might set up a mysql-server on the raspberrypi to hold the
> database?
>
> Any hint is highly appreciated.
>
> Tonio (Digikamuser for 10+ Years)
Locked
