All of the podcasts tracked by podstash are stored in an archive. You can create a new archive with the `podstash init` command.
Have you ever lost a podcast? Perhaps the author decided to stop paying for hosting.
Have you ever wanted to go back and listen to the first episode of a podcast only to realize that the feed only contains the last 100 or even 50 episodes?
Are you a digital hoarder?
If you answered yes to any of the questions above, then podstash might be for your.
Podstash tracks multiple podcast feeds and archives media files locally so that you never have to worry about losing access again.
For each tracked podcast, podstash keeps a snapshot of all the observed versions of the podcast's feed and the corresponding media files. It then combines the historical feed snapshots into a single unified feed that references your locally cached media and every episode from the podcast.
Along with the generated feeds podstash generates HTML files that provide an interface for exploring and listing to your newly acquired MP3 hoard.
You can install the latest version of podstash via npm:
npm install -g podstash
You can also build locally using yarn:
git clone git@github.com:fimad/podstash.git
cd podstash
yarn build
./dist/podstash --help
All of the podcasts tracked by podstash are stored in an archive. You can create
a new archive with the podstash init command.
podstash init --archive ./path/to/archive --base-url http://example.com
Podstash expects that your archive is exposed over HTTP. The URL that
corresponds to this is given in --base-url. If you haven't set up an HTTP
server, no worries, you can provide a made up value now and change it later.
You use the podcast add command to start tracking a new podcast.
podstash add \
--archive ./path/to/archive \
--feed-url 'https://example.com/podcast/rss.xml' \
--feed-name some-name
The name of the feed must be a unique and file system safe directory name.
The podstash update command directs podstash to fetch new RSS snapshots,
download audio files, and regenerate your mirrored RSS feed.
podstash update --archive ./path/to/archive
Podstash uses config files that are stored in the archive. If you change a
configuration file you must run podstash update for the changes to be
reflected in the generated feed/HTML.
The URL that points to where the archive directory is exposed over HTTP. This is
the value provided via --base-url when initializing an archive.
A mustache template that is used to inflate the archive's index HTML file. This file is optional and if it is not provided the default template will be used.
See the default template for an example.
A mustache template that is used to inflate each podcast's index HTML file. This file is optional and if it is not provided the default template will be used.
See the default template for an example.
The URL that points to the podcast's RSS feed. This is the value provided via
--feed-url when adding a new podcast to an archive.
FAQs
All of the podcasts tracked by podstash are stored in an archive. You can create a new archive with the `podstash init` command.
We found that podstash demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.
Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.