← Directory

Komf

Komf is a Metadata Fetcher for Komga and/or Kavita.

  • Media Applications
  • Media Servers
  • Network Services
  • Other
  • Tools & Utilities
Komf is a Metadata Fetcher for Komga and/or Kavita. You can let it run in the Background to update new added series or Connect to it's API directly and/or use the userscript to update directly in the Komga WebUI.(https://github.com/Snd-R/komf-userscript) Note that this is an API Container so there is no WebUI. Setup: Add Container as usual. Add the application.yml to the config folder (if it wasn't automatically added). Remove the Komf or Kavita Parts of the yml, when you aren't planning on using them. The .yml is in the top Post of the Thread (https://forums.Unraid.net/topic/124326-komf-docker-support-thread/).

Platform availability

Available on 2 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

15/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data

Based on 2 of 4 factors.

Availability: platform listings confirmed today, links checked 15 days ago

No GitHub repository data collected yet.

Checked 17 days ago - source: GitHub (BigBearTechWorld/komf)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set your Komga and Kavita details Before starting Komf, replace the Komga and Kavita web addresses, login, and secret API key values in the Docker command with your own media server details. If these are wrong, Komf will not be able to connect to those servers to find books or send notifications. source
  • Use a real, writable folder for /config Replace /path/to/config with an actual folder and, if you get permission problems, adjust the -u 1000:1000 values (the user and group IDs the container runs as) so the container can write there. This folder holds your settings, so if it is not available or writable, Komf may fail to start or lose its setup. source
  • Open the 8085 port you map The example maps port 8085 to 8085; a port is the network number clients use to reach Komf. If you use a different port, keep that port reachable, or you will not be able to connect to the running Komf. source

Fetched 16 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I point Komf at my Komga or Kavita server?

Replace the Komga and Kavita web addresses, login, and secret API key values in the Docker command with your media server details before starting Komf. If these are wrong, Komf will not be able to connect to those servers to find books or send notifications.

What should I do if Komf cannot start or loses its setup?

Use a real writable folder for /config, and if permission problems occur, adjust the -u 1000:1000 user and group IDs so the container can write there. The folder holds settings, so if it is not available or writable, Komf may fail to start or lose its setup.

Which port must be reachable for Komf?

The example maps port 8085 to 8085. If you use a different port, keep that port reachable or you will not be able to connect to the running Komf.

Answers sourced from github.com

Community

Collected 16 days ago - public community threads