Moving podget to another computer --- which files?
A simple podcast aggregator.
Brought to you by:
davevehrs
Menu
▾
▴
Hi,
I want to move my podget data ($HOME/.podget + the downloaded files) from one computer to another while preserving its own record of what has already been downloaded (so it doesn't download old podcasts again). Where does podget store that record --- just in the directory that DIR_LOG points to?
Thanks.
Podget's "memory" is completely held in the DIR_LOG directory. If you maintain that onto the new system then Podget will remember all files that it has downloaded from the earlier machine.
Moving $HOME/.podget is a good idea but not crucial to maintaining the "memory". You can update the podgetrc and serverlist files as you wish for the new system.
Good Luck and let us how it goes!
Dave
Charles,
First, let me start by saying you are very lucky that Sourcforge notifies me of any posts here. As it says on the main page for Podget, I have moved development to https://github.com/dvehrs/podget.
Now if I'm interpreting your question right you want to move the previously downloaded files and logs to a new PC. The first thing we need to know is where the files were downloaded to on the old PC. Generally that can be found in your podgetrc file in the DIR_LIBRARY configuration option. While we are there, check if DIR_LOG is set to a custom directory or if left unconfigured for the default. If DIR_LOG is the default then we only need to move one directory to get the old files and logs to a new system. If it is customized then we need to move two.
Let's assume it's the first simplier case and DIR_LOG is not customized.
By default Podget stores the DIR_LIBRARY within your HOME directory so if your username was "Charles", it would be default be in /home/Charles/POD.
By default the DIR_LOG directory is stored within that one at /home/Charles/POD/LOG. So this is why it makes it easy for us to move both at once.
Now to move that directory to a new PC, we can use something like scp. First we log into the old host in our HOME directory and from there run "scp -r POD NEW-HOSTNAME:", this will recursively copy the entire POD directory and it's contents from the old host to the NEW one.
This assumes you have the SSH client installed on the old host and SSH server installed on the new host.
...
Of course there is one other alternative that is often easier than copying all the data over. If you have copied the configuration directory over and have automatic cleanup enabled so you only need the most recent files from your podcast feeds, then we can skip everything above by just running one podget command. The trick here is knowing how many days you have configured the automatic cleanup to and how many new items per day that the feed provides. For this example, we are going to assume the feed delivers 1 item a day and you have automatic cleanup set for 7 days so we need the 7 most recent items.
Then on the new host all you need to manually run is: podget -vv --recent 7
This downloads the 7 most recent items and marks everything else in the feed as "already downloaded". So the next time podget runs, it only gets anything newer than that what it thinks it already got.
...
In my experience the second method does what I need when I move to a new system. For the podcasts I follow, there are very few that I want to archive old shows forever.
Good luck and let me know if you have any other questions,
Dave
If anyone wonders who "Charles" was, I have marked his posts as spam because he wasn't asking serious questions but rather attempting to use these forums to increase the links to his own product. It is not a competing product to Podget but his posts got discarded because he was being deceptive.