NAME

Podget

SYNOPSIS

podget <options> [command]
podget -h | --help

DESCRIPTION

OPTIONS

-c, --config <FILE>Name of configuration file.
-C, --cleanupSkip downloading and only run cleanup loop.
-d, --dir_config <DIRECTORY>Directory that configuration files are stored in.
-f, --forceForce download of items from each feed even if they've already been downloaded.
--import_opml <FILE or URL>Import servers from OPML file or HTTP/FTP URL.
--import_pcast <FILE or URL>Import server from iTunes PCAST file or HTTP/FTP URL.
-l, --library <DIRECTORY>Directory to store downloaded files in.
-r, --recent <COUNT>Download only the <COUNT> newest items from each feed.
-s, --silentRun silently (for cron jobs).
-v, --verbosity <LEVEL>Set verbosity level (0-3).
-h, --helpDisplay help.

EXAMPLE CRON JOB

Once podget is running acceptably, its most useful if you run it from a cron job so that the new songs are available to play or load onto a portable player and you dont have to wait for them to download.

To edit your crontab, do:

$ crontab -e

Then insert one line (i for insert mode), like the following:

15 04 * * * /usr/bin/podget -s

This will run podget at 4:15 AM every day.

AUTOMATIC CLEANUP

You can enabled automatic cleanup with every run by configuring it in your $HOME/.podget/podgetrc file. Simply set the following options:

  # Autocleanup.
  # 0 == disabled
  # 1 == delete any old content
  cleanup=1

  # Number of days to keep files. Cleanup will remove anything
  # older than this.
  cleanup_days=7

However, some people prefer to run cleanup as a seperate cron session. To do that, set the options in .podgetrc to:

  # Autocleanup.
  # 0 == disabled
  # 1 == delete any old content
  cleanup=0

  # Number of days to keep files. Cleanup will remove anything
  # older than this.
  cleanup_days=7

And add a cron job to run cleanup, like one of these examples:

  # Once a week on Sunday at 04:15AM
  15 04 * * Sun /usr/bin/podget -C

AUTHORS

Dave Vehrs