Closed SamTV12345 closed 1 month ago
Every time I start your container, I get this error:
Attaching to podfetch-podgrabv2-1
podfetch-podgrabv2-1 | thread 'main' panicked at 'sqlite::/./db/podcast.db: NotPresent', src/config/dbconfig.rs:8:49
podfetch-podgrabv2-1 | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
podfetch-podgrabv2-1 exited with code 101
This is my docker-compose.yml
version: '3'
services:
podgrabv2:
image: samuel19982/podgrabv2:latest
ports:
- "9514:8000"
volumes:
- /medien/podcast:/app/podcasts
- /docker/podfetch/podfetch.db:/app/podcast.db
environment:
- POLLING_INTERVAL=240
- SERVER_URL=http://localhost
I tried to start with a fresh directory for podfetch and I tried to copy over to old DB from podgrab. Nothing worked for me
I tried to open an issue in your repository, but it needs to much information, I use docker, not npm
Thanks for pointing out this issue. Please try again with your configuration and change the line /docker/podfetch/podfetch.db:/app/podcast.db to /docker/podfetch/podfetch.db:/app/db/podcast.db
It was an error from my side which was triggered when the DATABASE_URL environment variable was not set. This is fixed now and the variable is not required and defaults to the value in the documentation.
I added some more features like a redesigned podcast view, more information about the podcast itself like tags, language and description.
@SamTV12345 Is it a drop-in replacement for podgrab? Can I just point it at the existing db and files?
Unfortunately not. I had to make some modifications to the database to accommodate the new features. But you can export from podgrab as opml and import into PodFetch as opml.
OK, will it need to grab all the mp3's again, or will PodFetch recognise those as existing already?
It only loads the first 5 podcasts. If you want to keep them you need to adapt them to the scheme. I write the podcast directory like the title with only ASCII literals and no spaces. So if you stick to that scheme it won't download them again.
It seems really sketchy to just use a issue in this project to advertise your own just similiar project, especially with the title "New repository". You use a complete different code, in a complete different language and you do have no migration available, how can you you use this title? How should the user trust you?
You really understood the thought of open source. Yes I advertise my project to make more money - no I simply wanted a replacement and could get a lot of people to help me build a better "podgrab" server that is actively maintained. I am happy for any contribution but don't want to participate in any hate train that complains that I do "advertising" in the issues of another project. I wish you a wonderful day and hope you will find peace.
It has nothing to do with open-source to post ads for your project in other projectswith the title "New repository" to trick people into thinking the owner moved the repository. Why wouldn't you just say "I build a similiar project" (and even that would be spam)? And I had a look at your project and at least for archiving, it's much worse, even today.
My project has become the defacto standard for podcast listening.
My project has become the defacto standard for podcast listening.
No offence but your project has 337 stars, Audiobookshelf has over 6200. It is for audiobooks and podcasts
I think Audiobookshelf is more defacto standard than your project
I created a new repository that basically contains all features from this repo. Feel free to contribute. I will review prs as fast as possible.