C3004 Posted June 1, 2022 Share Posted June 1, 2022 (edited) To be moved to DockerContainer support. Ask here for any Problems that might show up during Komf-Docker installation or usage. Komf replaces all Metadata from what you're modifying! Installation: It's the same like you know for other Containers. Fill in The required Fields and ignore the others when not needed. Config: In the current docker the application yml is not provided. So I put it here application.yml(31.12.22) for you . You need to put it in Komf's Appdata folder. There you can take a look at the advanced settings. Info: Komf is currently an API project only. Unless you know how to deal with those you can join me in using the Userscript. The Script adds a new button on the right of the usual config buttons in Komga: It will let you Identify the Series and add Metadata to it. Preparation Userscript: You will need a Userscript manager. I took Snd-R's recommended one named Tampermonkey. Download the Userscript from his Release-Section. Open the Settings from Tampermonkey. Drag and drop the js file in there. Press the install button. Now you should see the Script in the installed Section. Press the edit button on the far right. 1. Change the first URL to your Komga-Instance. 2. Change the second URL to your Komf-Instance. Now save the changes under File. You can now reload your Komga Tab and enjoy the Metadata Grabber. General Links: Github-Repro-Komf-Docker: https://github.com/Snd-R/komf Github-Repro-Komf-Userscript: https://github.com/Snd-R/komf-userscript Github-XML-Template: https://github.com/C3004/Unraid-Templates-C3004/blob/main/Komf-Docker.xml Github-Repro-XML-Templates: https://github.com/C3004/Unraid-Templates-C3004 Edited December 31, 2022 by C3004 updated yml Quote Link to comment
Eraydien Posted June 2, 2022 Share Posted June 2, 2022 (edited) Once I have the script installed, where in the UI do I see the option to add data? User error, I got it working now! Actually, it's not working. It's saying "no match found" for every single comic series I scan. 2nd edit: The metadata is did grab automatically was laughably wrong. Edited June 2, 2022 by Eraydien Quote Link to comment
Steven O'Connell Posted February 13 Share Posted February 13 Docker refuses to start with the following error: 13:03:09.689 [main] ERROR org.snd.Application - Failed to start the app java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but no scheme was found for at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1261) at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1634) at org.snd.module.MediaServerModule.<init>(MediaServerModule.kt:96) at org.snd.module.AppModule.<init>(AppModule.kt:29) at org.snd.module.context.AppContext.refresh(AppContext.kt:39) at org.snd.module.context.AppContext.init(AppContext.kt:29) at org.snd.cli.Komf.run(Komf.kt:30) at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:198) at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:18) at com.github.ajalt.clikt.core.CliktCommand.parse(CliktCommand.kt:400) at com.github.ajalt.clikt.core.CliktCommand.parse$default(CliktCommand.kt:397) at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:415) at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:440) at org.snd.ApplicationKt.main(Application.kt:20) Not sure What to do, as far as I can tell I've filled out all requires fields correctly in the "application.yml" and docker template. Quote Link to comment
C3004 Posted February 15 Author Share Posted February 15 Hi Steven, i took a short look. Could replicate the error. Currently it seems to me that the docker won't accept that the Kavita fields are not filled in. The Docker normaly should ignore kavita if the event listener is not activated. I'll take a closer look later. Anyway the latest version without kavita would be this one sndxr/komf:0.12.0 but it's not kompatible with the new config. Quote Link to comment
EVERGREEN Posted August 23 Share Posted August 23 I am also running into this. I don’t have Kavita but filed the fields out with bogus strings. Quote Link to comment
VodkaPump Posted September 21 Share Posted September 21 The above issues are caused by the application.yml file not being generated by the docker. Make one in the mounted config folder following the readme from the projects github and you'll be all good Quote Link to comment
maknilsin Posted September 27 Share Posted September 27 Also running into this issue. Has anyone been able to resolve this? Even adding the application.yml file doesn't seem to sort it out on my end. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.