Guspaz wrote:
Why would this require an upgraded linode? For more disk space? Podcasts don't use much space; 16GB of space on a cheap linode would provide somewhere between 291 and 1165 hours of podcasts, depending on bitrate.
I'm not concerned about storage, it's bandwidth. I am going to have two sites on the Linode (one of which is the podcast site), the podcast audio, and I plan to setup a private Minecraft server to play with a couple friends.
EDIT: I'll be uploading four copies of the audio too. Not for redundancy, just to support both MP3 and Ogg Vorbis, and to have a high-bandwidth version and low-bandwidth. I just like to cover all sides when possible, and I know there will be listeners who will be redundant in downloading all four copies.
hoopycat wrote:
The nice thing about a podcast is that it's just a pile of static content; hosting one isn't too laborious.
I'd probably try django-podcast first, and work from there. It uses its own XML templates instead of building atop the standard feed generator. It also uses the standard FileField for enclosures, so if hosting it does stress your bandwidth, using S3 or some other object storage provider should be a minor config change with django-storages.
Certainly worth checking out.