u/zittoone

Please open an issue with your struggle, I'd be more happy to make it easier for the next person thanks to your feedback.

Really appreciate your comment, thank you.

I completely agree with you. This is not something you must use, and there are better alternatives out there, or even not using it at all might be better choice depending on the situation.

I'm building tools firstly for myself, and I like not being able to scale vertically. I like maximizing my resources, and so far a Raspberry Pi 4 is handling my cluster very well.

I'm using sablier precisely for this, I'm not using all my services at once, quite the opposite. Having idle services being throttled is giving me a very smooth experience on the services I'm actively using.

Another usage is automated clean up of services accessed once in a month. It something that is real, even more in professional environments with dev/qa/staging environment.

This is using exactly the primitives you mention here.

Instead of have a flat limit all the time, you have a limit that depends on the service being used, which is very powerful for constrained environments.

So I've been running Sablier for a while now on my raspberry pi and basically you never really save compute (thus power) anyway.

What it does though, is the ability to define an idle state on other containers that will be scaled down so that you avoid the neighbors problem.

I'm a minimalist, I try to fit as much as I can on the (almost) smallest homelab: a raspberry pi 4.

I've run into throttled disk messing up with my feed on Plex, which lend me into adding the blkio scaling mode.

Add that with the anti-affinity pattern and you can really avoid any neighbors problem.

Haha, hard agree that the documentation was bad...

Hopefully you will agree with my "was" haha.

Since then I've learned about https://diataxis.fr/how-to-guides/ which is a great read.

For the website, I'm using a Hugo template: https://imfing.github.io/hextra/docs/ and matching my theme (orange).

As mentioned in the post, I started this project back in 2020, while choosing the flare, I felt that "Project Showcase: Software - Mostly AI Generated" was not true, the project is not AI Generated. For sure it has received a lot of AI contributions recently.

I'm transparent with AI usage, I'm positive that AI usage should be disclosed, and it's also why I'm not trying to hide any contributions from the AI watermarks.

https://preview.redd.it/pn79o38w75yh1.png?width=533&format=png&auto=webp&s=936e933fec468c04c1eb0086fa26f6b3d2807aec

Mmmmmmmh

This post was written with the help of Claude to summarize the changes over the last 4 years.
The Sablier project itself has a lot of contributions from me and external contributors using AI coding agents.

Mail envoyé, merci pour l'initiative

yeah if you want to watch stuff the TV wins for sure

but the big difference for me: a TV has to be plugged in and switched on all day to show a picture, and it glows. this one isn’t on an outlet, and it doesn’t emit any light, it just looks like a print on the wall. you kind of forget it’s tech

also, one of the reasons I built it: I live abroad, far from my family. we send each other photos all the time, but they just get lost in our phones. now they send me a photo and it shows up on my wall, and I do the same for them

on the price, I understand you. color e-ink is still pretty new and the technology behind it still expensive. we really hope it gets cheaper over the next few years, and we want to take part of this change now

so not a TV replacement, more like a frame that keeps up with how we share photos now

What about https://github.com/kimdre/doco-cd ? I'm using doco-cd both for selfhosting my personal stack and one of my small professional project. So far it's been perfect.

• Internal corporate documentation: everyone reading it must have a license, even non developers
• Internal datasource content: github pages uses distinct API token which you cant generate using PAT, Fine grained tokens or GitHub App tokens.

Bigger than 13" is too much PIA right now. The bigger Spectra 6 panels are just not worth it yet.

The 10" has a new TCON and has a better retail price than The 13".

My opinion: wait for new panels to come out.

The 10" spectra 6 has a new display controller which natively support this way of refreshing the pixels. It is called the "ripple" effect.

It is less efficient than the tradional blink refresh, but it is more pleasant to look at.

The blink refresh has been criticized a lot by customers of spectra 6 based products, at some point people thought their frame was broken.

Maintainer here!

I'm trying my best to document everything, it does work in k8s.

Please open an issue with issues you've encountered to help me, thanks!

I'm curious to see too

What kind of standards are you thinking of ?

Wow, it actually does look like it!!! Thank you very much