# kill-the-newsletter

I gave in and just created kill-the-newsletter RSS feeds on the official service for the few newletters I have that aren’t RSS-able. The cost of increasing my vps size was more than I was able to justify for just a few RSS feeds.

Since setting it up it’s been working great and I have no complaints. As long as they keep it up and running, I should be good.

# RSS Reader

I went back through the list of apps that support FreshRSS on their GitHub page and gave Fluent Reader a try and I like it so I think I’ll stick with it. Haven’t used it on my e-reader yet but it’s not too heavy on animations which is where I feel like e-readers struggle.

# Eleventy

I played around with an Eleventy installation through Yunohost. I really like how quick it is and the ease of just being able to write individual Markdown files to get content published.

Unfortunately their Yunohost app is a little old (maybe) or at least restrictive when I tried to convert it to use their blog template project.

The core issue I had was with the configuration file. In Yunohost it lives far away from the content and published directories and I had to do a fair bit of tweaking to get everything to resolve correctly.

The next big issue is the challenge of getting the content up to the vps. It’s not super convenient to have to ssh and to write a new post.

My thoughts to get around this when I have some more time to try again is to get the content directory set up as a git repository controlled by Gitea which is also running on Yunohost. If I can get Gitea to save the file in the correct place or point the Eleventy config to where Gitea stores it’s files, I’ll be able to manage it from anywhere I can use git.

So I’m getting closer but the journey continues. And I think that’s what this is, a journey. If I just used a hosted solution it would be much easier but probably not as much fun.