Readbeanicecream has a new home!

Due to some instability issues with surge.sh, I have decided to migrate my blog to Codeberg.org. Update your RSS feed and follow along.

- Home: https://readbeanicecream.codeberg.page/
- RSS: https://readbeanicecream.codeberg.page/feed_rss_created.xml

Looking forward to seeing you there!

#blogging #blog #blogs #bloggers #indieweb #smallweb #personalsites #rss #foss #opensource #codeberg

ReadBeanIceCream

@readbeanicecream FYI, Codeberg Pages is in maintenance mode and very regularly serves 5xx errors, certificate issues, etc. I tried moving my blog there, then within a month I had to move again.

https://codeberg.org/Codeberg/pages-server/issues/399

We will not accept new features! The project is now in maintenance mode.

The pages-server has a lot of issues and is subject of many discussions. I am currently the single maintainer of this service and it is just to much for me alone to get behind the magic of all the parts of the code and find the reason behind and fix all the issues people find. There is also an in...

Codeberg.org

@teotwaki @readbeanicecream

There's a V2 (full rewrite) in use for quite some time already. This repo isn't in use anymore.

@readbeanicecream

Surge.sh really isn't a good place for a production website. It's badly maintained and has a somewhat unclear overall scope.

@pat_dev I really like surge.sh. When it works, it works well. I was also patient with the outages since the service is free and my blog is not exactly required for my survival.

But, during the last extended outage, I said I would move to something else on the next one. This outage was the time.

I still like surge.sh, but I will give codeberg a try for awhile.

@readbeanicecream I keep seeing the word Codeberg everywhere and I never before knew what it was, so it's interesting for me to finally know. And it does the RSS feed automatically? That sounds pretty stellar. I only wonder whether it does the job of aggregation at any point.
@dckim Codeberg is just a code repo. I build my blog with mkdocs-material then push to codeberg using git.
@readbeanicecream that sound pretty similar to my documentation setup then. The only thing I had a bit of an issue with was setting up versioning so that there is never a caching issue after I push an update. It seems okay now.