Generate an RSS feed from a config file and an mp3 file.
Go to file
Ismael Arenzana 70dbddb817 README and changelog 2020-11-06 16:46:57 -05:00
cmd Fixes owner email, explicit tag and some categories. Takes multiple configs 2020-11-06 16:41:27 -05:00
examples Fixes owner email, explicit tag and some categories. Takes multiple configs 2020-11-06 16:41:27 -05:00
objects Fixes owner email, explicit tag and some categories. Takes multiple configs 2020-11-06 16:41:27 -05:00
vendor Fixes owner email, explicit tag and some categories. Takes multiple configs 2020-11-06 16:41:27 -05:00
web Better web 2020-11-04 15:21:16 -05:00
.gitignore add/generate work 2020-10-28 18:06:10 -04:00
CHANGELOG.md README and changelog 2020-11-06 16:46:57 -05:00
Dockerfile Initial commit 2020-10-27 12:55:32 -04:00
LICENSE Initial commit 2020-10-27 12:55:32 -04:00
Makefile Initial commit 2020-10-27 12:55:32 -04:00
README.md README and changelog 2020-11-06 16:46:57 -05:00
VERSION Initial commit 2020-10-27 12:55:32 -04:00
go.mod Basic S3 implementation 2020-11-02 16:16:52 -05:00
go.sum Basic S3 implementation 2020-11-02 16:16:52 -05:00
main.go Initial commit 2020-10-27 12:55:32 -04:00

README.md

feeder

Generates RSS feed and can upload to S3. Also, it can generate episode and index HTML if desired.

Install

Build from source

Make sure Go 1.15+ is installed on your machine. You can follow this guide to do so. On a Mac, just set your $GOPATH and run brew install go.

git clone https://gitlab.com/iarenzana/feeder.git
cd feeder
make

Now you can execute feeder.

Examples

First, add an episode:

feeder add -f ~/episode01.mp3 -u

This will generate an entry on the podcast_episodes file. We should edit the JSON file with the info we want first. The episode has also been uploaded at this point (it could have generated an episode file too if we had passed the -w option).

Now we need to generate the RSS file from the episodes:

feeder generate -c ~/feeder_podcastname.yml -u -w

This will generate the RSS file and upload it to S3.

It's recommended that you create a CloudFront distribution and point Route 53 entries to it rather than just going directly to the S3 bucket.