This is backed up to an online backup disk daily, and offline USB-disks weekly (the offlines are a set which are rotated out of the house). So all my data to one easy to backup volume.
Digikam manual manual#
Please consult the manual for full details, including picture formats supported. DigiKam supports import of photos from cameras, creation of albums, tagging with dates, subjects and other properties, and excellent search facilities. The folder /usr/local is actually a bind mount of /home/local. View, manage, edit, enhance, organize, tag, and share photographs. I aim to keep all my stuff in /home or /usr/local. The backup script uses notify-send to inform the desktop that the backup is in progress or is being skipped due to to digikam being active - that way I only create consistent backups, and I won't accidentally start digikam until the backup finishes. This helps if anything goes badly wrong with the database/config files (which has only ever happened once due to a mistake I made when playing with digikam settings). On each login (approximately once per day) I have a backup script that checks if digikam is running, if not it backs up the database folder and other config files to a tar. Eventually I bought a 2 TB SSD which could easily fit my photos, the database, and all my other accumulated non-photography stuff. I switched to mariadb on SSD when the photos on the disk grew beyond 500 GB and the scans for new items started to take a large amount of time. Specified in the corresponding Arch Linux package.I have digikam using mariadb with the database stored in a folder in my home directory which is on SSD.
Digikam manual license#
License, except for the contents of the manual pages, which have their own license The website is available under the terms of the GPL-3.0 Using mandoc for the conversion of manual pages. Package information: Package name: extra/digikam Version: 7.7.0-1 Upstream: Licenses: GPL Manuals: /listing/extra/digikam/ Table of contents AUTHORĬleanup_digikamdb was written by Andi Clemens 24 October 2011 This eliminates free pages, aligns table data to beĬontiguous, and otherwise cleans up the database file structure. The VACUUM command cleans the main database by copying itsĬontents to a temporary database file and reloading the original databaseįile from the copy. The full documentation for digikam is maintained as a html manual in the. Inserts, updates, and deletes can cause the information in the database toīecome fragmented - scrattered out all across the database file rather than But in the meantime, theĭatabase file might be larger than strictly necessary. Next time new information is added to the database. When an object (table, index, or trigger) is dropped from theĭatabase, it leaves behind empty space. If more then oneĭatabase is found in this location, cleanup_digikamdb will optimizeĮvery database found in this path and below.įor further explanation, see the following description of the Invoking the sqlite command ' VACUUM ' on it. In a final step the database will be optimized by It then will read the digiKam configuration file and determine theĭatabase location. The program will make sure that no instance of digiKam is running,īecause it is more safe to have no database access during the optimization Size and an increased access speed, because unneeded elements are removed This will, in most cases, lead to a smaller database file DESCRIPTIONĬleanup_digikamdb will cleanup and optimize the digiKamĭatabase file. Specified path is invalid, the entry from the configuration file
p path Specify a different database path. Cleanup_digikamdb - Cleanup the digiKam databases to reduce their
0 kommentar(er)
