mgdigital

Hi @hunmar , I think the 2 error messages you posted may be separate issues. The first I think was fixed in https://github.com/bitmagnet-io/bitmagnet/pull/139 Are you still seeing either of these...

Thanks @kovalensky . Support for v2 is currently way down the roadmap as it will present a significant technical challenge for (currently) relatively little benefit as far as I can...

I just don't think the performance would be good enough for large indexes, though I appreciate it would be convenient in theory. Most apps using a sqlite DB are not...

> Hi, and thanks for considering this. If I understand correctly your solution using `embedded-postgres` also achieves the same purpose as `sqlite` in that we can release a `bitmagnet` container...

Tags and resolution are filterable. This is separate from the search query string. I don't know that it needs additional support within the query string (or that it doesn't). I'm...

> Just wondering if it's not better to use an Elasticsearch or similar, instead implement the whole search in the Postgres It's a trade-off. Yes, something like Elasticsearch could offer...

That is very strange; the IDs seem to be coming from the Gorm ORM like that, but those short IDs are definitely not the ones in the DB, where it's...

Currently on the FAQ page we have: > You should allow roughly 50GB of disk space per 10 million torrents, which should suffice for several months of crawling, however there...

I've checked just now and am on 67GB for 13.5 million torrents. A couple of things to bear in mind: - Saving content data is one reason more space is...

Hi, can I ask what version you upgraded from? If it was prior to 0.5.0 you may have the reindex job running that was part of this upgrade.... The /metrics...