> When modifying the rip.properties file to change "log.save" to true I can't find where the log is being written
It should be in the dir ripme was started from
> So where does the log get written?
No idea, but if you find out leave a comment and I'll update the wiki
> Where is the canonical list of all the available options?
> I was unsure if it was being updated with each release. Does the docker container get updated with each release?
It should be but it does sometimes get forgotten. It's easy enough to do by hand via editing the docker file
> Is this what I should be using, or is there another docker container that is kept more up to date?
The official docker is https://github.com/RipMeApp/ripme-docker
> Also how would I go about changing the properties file permanently for each container?
I;ve not tried it but docker exec -it <container> bash
should start bash in the container. From there just edit ripmes config file
Thanks for the reply. I was planning on doing something like that anyways so it should work out for me.
A quick question about the wiki, did ripme used to rip the files from URLs directly in the past, but that was a feature that was taken out? I am asking because one of the flags for using ripme says that you can rip URLs from a file
usage: java -jar ripme.jar [OPTIONS] -4,--skip404 Don't retry after a 404 (not found) error -d,--saveorder Save the order of images in album -D,--nosaveorder Don't save order of images -f,--urls-file <arg> Rip URLs from a file. <---
> After a user has been ripped, another script calls jdupes to look for duplicate files leaving symlinks in place so ripme does not re-download them
Why not just use the remember.url_history
feature? It will remember all the file urls ripme downloads and skip them in future rips
Anyhow it is currently no possible to change this behavior but there should be. I've filed an issue here and will get on fixing this for the 1.7.62 release