uuid: - value: 43f35613-9c2f-46e9-b581-8253823fb7d8 langcode: - value: en type: - target_id: daily_email target_type: node_type target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7 revision_timestamp: - value: '2025-05-11T09:00:03+00:00' revision_uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 revision_log: { } status: - value: true uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 title: - value: 'Self hosting the Beyond Blocks podcast' created: - value: '2024-12-18T00:00:00+00:00' changed: - value: '2025-05-11T09:00:03+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2024/12/18/self-hosting-podcast langcode: en body: - value: |
As part of my recent digital simplification, I've started hosting the episodes of the Beyond Blocks podcast myself.
I've always had the podcast pages on my website and used them as the primary pages to redirect people for information about the episodes.
I embedded an audio player from a third party service that were hosting the files, but have replaced it with the native HTML audio element.
It's simpler, but I like it.
My website is built with Sculpin, so I was able to do this easily with Twig by adding the path to the MP3 file to each episode:
<audio controls>
<source src="/files/bb/episodes/{{ page.episode_filename }}" type="audio/mp3">
</audio>
This is already live. You can see it on any of the podcast episode pages.
The other thing I'm using is the feed that publishes episodes to Spotify, iTunes, etc.
But I have all the information and ability to create this myself.
This part is still in development and I'll need to test it before switching to it, but it will mean the feed URL will change and people may need to resubscribe.
Using a hosted service was a great way to get the podcast up and running quickly, but I'm looking forward to having more control over it, even if it involves a little upfront development work.
But, it will make it easier to post future episodes as I'll be able to do it all in one place.
I have some new guests lined up for 2025, which I'm looking forward to.
If you want to be a guest on the podcast or want to make a suggestion for someone I should have on, reply to this email and let me know.
format: full_html processed: |As part of my recent digital simplification, I've started hosting the episodes of the Beyond Blocks podcast myself.
I've always had the podcast pages on my website and used them as the primary pages to redirect people for information about the episodes.
I embedded an audio player from a third party service that were hosting the files, but have replaced it with the native HTML audio element.
It's simpler, but I like it.
My website is built with Sculpin, so I was able to do this easily with Twig by adding the path to the MP3 file to each episode:
<audio controls>
<source src="http://default/files/bb/episodes/%7B%7B%20page.episode_filename%20%7D%7D" type="audio/mp3">
</audio>
This is already live. You can see it on any of the podcast episode pages.
The other thing I'm using is the feed that publishes episodes to Spotify, iTunes, etc.
But I have all the information and ability to create this myself.
This part is still in development and I'll need to test it before switching to it, but it will mean the feed URL will change and people may need to resubscribe.
Using a hosted service was a great way to get the podcast up and running quickly, but I'm looking forward to having more control over it, even if it involves a little upfront development work.
But, it will make it easier to post future episodes as I'll be able to do it all in one place.
I have some new guests lined up for 2025, which I'm looking forward to.
If you want to be a guest on the podcast or want to make a suggestion for someone I should have on, reply to this email and let me know.
summary: null field_daily_email_cta: { }