Pod Local Sync
This utility allows you to manage a podcast RSS feed locally and spin up a small server to sync it with podcast applications like macOS' Podcast.app.
I wrote this since in macOS Catalina (10.15), it is no longer possible to manually add local files to the app.
How to
Python 3.8 is required.
pip install podlocalsync
podlocalsync works in the current directory and will automatically pick up
files.
To start, you need an image for the feed in the current directory:
$ podlocalsync init
Feed title: My Feed
Using image myimage.png.
This will create feed.toml, which stores the information about the feed.
Next, you can add episodes. podlocalsync will look for *.m4a and .mp3
files. The publication date is also filled in from the file time.
$ podlocalsync add
Episode audio: [episode-1.m4a]:
[0] episode-1.m4a
[1] episode-2.mp3
[2] episode-3.m4a
>
Episode title: My Episode about Cats
Episode publication date: [Fri, 31 Jul 2020 06:26:31 +0000]
If you've added an episode, it will be excluded from the next add.
Finally, you can serve the feed locally. This will create or overwrite
feed.rss and spin up a server:
$ podlocalsync serve
http://localhost:8000/feed.rss
^C
Keyboard interrupt received, exiting.
You can subscribe to this URL in a podcasting application, although the server isn't intended to be run for a long time, and certainly don't expose it to the internet.
If you want to subscribe from e.g. an iPhone, use your computer's IP address as the hostname (and make sure the firewall allows connections):
$ podlocalsync serve --host 192.168.1.136
http://192.168.1.136:8000/feed.rss
License
This program is licensed under the GNU General Public License 3.0. For more information, see LICENSE.
Metadata
Release files for podlocalsync 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| podlocalsync-0.0.1.tar.gz | 16.8 kB | Without provenance | Details for podlocalsync-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| podlocalsync-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for podlocalsync-0.0.1-py3-none-any.whl |
Total release size: 33.6 kB
Release files / podlocalsync-0.0.1.tar.gz
| Download URL | podlocalsync-0.0.1.tar.gz |
|---|---|
| Size | 16.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ab21803900d5f346e6a21e29da2d9ca7016345b981e76216ca05025a59e8abc
|
|
BLAKE2b-256 checksum How to use checksums |
c127e64abba98b44c7073dce82225158ea6f915ec366b1066d14439f248f15da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.10 CPython/3.8.5 Linux/5.3.0-1032-azure
|
Release files / podlocalsync-0.0.1-py3-none-any.whl
| Download URL | podlocalsync-0.0.1-py3-none-any.whl |
|---|---|
| Size | 16.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f53327ac431238664d7de87f8d833883a1df0bad3b9e63a629bb199d13ed6f9
|
|
BLAKE2b-256 checksum How to use checksums |
d339be7cf61854f1255eff87b39b20694fff722fac1ad80a625dfee96f800d3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.10 CPython/3.8.5 Linux/5.3.0-1032-azure
|
Security for podlocalsync 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.