Bug 435349 - Install digikam on a synology nas
Summary: Install digikam on a synology nas
Status: RESOLVED DUPLICATE of bug 433929
Alias: None
Product: digikam
Classification: Applications
Component: Albums-Engine (show other bugs)
Version: 7.3.0
Platform: Other Other
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-04 16:56 UTC by Thomas Bach
Modified: 2023-10-23 14:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Bach 2021-04-04 16:56:50 UTC 
Is it possible to install digikam as a package directly on a synology NAS? At the meomen, i have stored my pictures on a NAS-Share und i am using Maraidb as database. Vut i am using the client on a W10 Machine and the performance is not so good. 

I know, that confugartion ist not recommended, but i can not find any tutroial to install the package on the NAS itself.

I try to access the photo with all Metadate from different devices.

I am using the replication mchnanism of the NAS for security and that works good. 

But it will be better to use web-client directly on the nas instaed of using the win client
Comment 1 caulier.gilles 2021-04-04 17:02:59 UTC 
Why to install digiKam on a NAS ? It's a server, not a client computer...
Comment 2 Thomas Bach 2021-04-04 17:09:16 UTC 
Synology has Linux as System. With a client on Windows, all traffic for changing Database and picture metadat are transferred over the lan. And that results in a poor performance. Also, if the system is isntalled directly on the nas, i can use it as web program from any device.

Please understand me right (instead of my bad english :- ). Digikam is the best produkt to manage photos i found in the last years. But i try to find the best solution for me.
Comment 3 Thomas Bach 2021-04-04 17:11:43 UTC 
And Synology has many packkages working as client
Comment 4 Maik Qualmann 2021-04-04 17:17:36 UTC 
*** This bug has been marked as a duplicate of bug 433929 ***