![]() Enable the Global privileges → Check all option, and press Go. Choose Any host from the Host name drop-down list. Specify the desired user name and password. Switch then to the User Accounts section and create a new user by clicking on Add user account. To do this, launch phpMyAdmin, switch to the Databases section, and create three databases: digikam, digikam-thumbnails, and digikam-recognition. Next step is to create a new database user as well as databases for use with digiKam. To manage the server and databases, install the phpMyAdmin application from the App Center. To do this on a QNAP NAS, launch the Control Panel, click SQL Server in the Applications section, and activate the Enable SQL server and Enable TCP/IP networking options. While many NAS models ship with the MySQL/MariaDB database server, you often need to activate it manually. Keep in mind, though, that if any of your neighbors get the same idea of using powerline adapters on their local networks, this will affect the overall speed of your network too. In that case, a couple of Gigabit powerline network adapters provide a less cumbersome solution. However, laying Ethernet cables around your apartment might not be particularly practical. Even the fastest WiFi connection is simply not fast enough, so a wired network connection is the only viable option here. First of all, you need a fast network link between the NAS and any machine that you want to use for working with your photo library. Switching to the NAS-based digiKam setup is a three-step process:īefore you proceed, though, you need to do some preparatory work. ![]() This allows you to access your photo library from any machine on the same network as well as keep your photo library safe thanks to the fact that storage on most NAS appliances is usually configured as RAID. Got a NAS? Still store your photo library and digiKam databases on a local machine? It’s time to take your digiKam setup to the next level by moving your photo library to the NAS and switching to the MariaDB (or MySQL) database backend. ![]()
0 Comments
Leave a Reply. |