Oh hai!
You can add a "release: 2" line to the article markdown in case you fudged up a release and would like to increment the GUID in the feed after a fix
You can add a "published: false" line to the article markdown to NOT have it show up anywhere.
Feed with all items:
/podcast_feed/all/m4a/rss.xml
Examples for the category feed generation:
/podcast_feed/spezial/mp3/rss.xml
/podcast_feed/talk/opus/rss.xml
iTunes feed that uses m4a with a fallback to mp3 if there is no m4a for that episode
/podcast_feed/talk/itunes/rss.xml
Note: You can also add a feed_size parameter and a page parameter to the URL ("?feed_size=4&page=3")
Prerequisits: install stork
For every release the stork index has to be built like this:
python gen-stork.py > stork.toml
stork --build stork.toml
then a github action builds and publishes bgt.st
to https://search.binaergewitter.de/bgt.st.
If you rename a post you should migrate the old comments. Since the id for comments is the post title: https://github.com/Binaergewitter/serious-bg/blob/main/serious/lib/site/views/_isso.erb#L8.
- Get the
comments.db
- Create a backup
- Look up the old id and new id in the
threads
table (i usesqlitebrowser
) - Run the update command
UPDATE comments SET tid=$newid WHERE tid=$oldid;
- Save file!
- Upload
comments.db
again
scp binaergewitter:/var/lib/isso/comments.db ~/Downloads/comments.db
cp ~/Downloads/comments.db ~/Downloads/comments_bak.db
sqlitebrowser
scp ~/Downloads/comments.db binaergewitter:/var/lib/isso/comments.db