Torrent-Tracker-Platforms VS danbooru

In that case, I would shop around different codebases before doing anything else (I’m a big Gazelle fan myself, but everyone I’ve ever worked with says learning PHP is a pain, which makes me a bit hesitant). HDVinnie has a good list here: https://github.com/HDVinnie/Torrent-Tracker-Platforms

https://github.com/HDVinnie/Torrent-Tracker-Platforms currently the easiest to deploy is UNIT3D,

Lazy or unskilled web administrators Most trackers use pre-made software. https://github.com/HDVinnie/Torrent-Tracker-Platforms

This project is for fun. Figured it would be a nice addition to my other three tracker related repos. https://github.com/HDVinnie/Private-Trackers-Spreadsheet https://github.com/HDVinnie/Torrent-Tracker-Platforms https://github.com/HDInnovations/UNIT3D-Community-Edition

Check out this github for links to the different tracker platforms that have been developed.

"Not so good update. We couldn't get money into the account quick enough (only had 11 days) and lost the domain, I've filled out the form that's currently at the sites address but no response yet. because of the license for the sites code we can't change the domain without paying at templateshares.net but the staff are never there any more so that's never going to happen. the only other option is to migrate the site to a new code base (https://github.com/HDVinnie/Torrent-Tracker-Platforms) which I don't have the skill to do and R [name removed] doesn't have the time to do so we are stuck in a pretty bad spot right now."

This is par for the course for me: I want to run this software

https://github.com/danbooru/danbooru

and the compose file “just doesn’t work” because it is a few years old and not compatible with the docker compose version installed with Ubuntu. I took a crack at updating the config file but didn’t find a lot of documentation to help…. And remember I’ve frequently had “simple” Docker installations become a matter of “download files for hours, have the installation fail, repeat…” so engaging with that monster at all seems like a risky time sink.

Really though an open source product has not really been released until there is documentation walking through setting it up and doing some simple thing with it. As it is I am really not so sure what it is, what kind of hardware it can run on, etc. Do you really think it got 117 Github stars from people who were qualified to evaluate it?

(I’d consider myself qualified to evaluate it.. If I put two weeks into futzing with it.)

Every open source release I’ve done that’s been successful has involved me spending almost as much time in documentation, packaging and fit-and-finish work as I did getting working it well enough for me. It’s why I dread the thought of an open source YOShInOn as much as I get asked for it.

Sometimes though it is just a bitch. I have some image curation projects and was thinking of setting up some “booru” software and found there wasn’t much out there that was easy to install because there are so many moving parts and figured I’d go for the motherf4r of them all because at least the docker compose here is finite

https://github.com/danbooru/danbooru

even if it means downloading 345TB of images over my DSL connection.

Danbooru is open source under a permissive license (https://github.com/danbooru/danbooru), so you can fork it and add features from there

Does this need to be a tracker? I think this might be better suited to an image board. You can look into running your own instance of Danbooru.

Danbooru itself is opensource: https://github.com/danbooru/danbooru