Émilien (perso)

Hello, Since this PR is just about migrating to Valkey and not nothing else, I have added back what has been removed: https://github.com/searxng/searxng-docker/pull/230/commits/f888ba3794940a2e3405dc935a3aa31f3fb71c8a Feel free to create another PR for...

Maybe I have merged this PR a bit too fast but why @inetol you didn't use these docker images instead: - https://hub.docker.com/r/valkey/valkey/ - or https://hub.docker.com/r/bitnami/valkey ?

> I thought I've mentioned this before, the reason for that is because the `valkey/valkey` image runs under root by default, which is not the case with the current Chainguard...

If we are going to allow every specific pages to be disabled, we might as well use an array for that like: ``` pages_enabled: trending: true popular: true search: true...

Would prefer in this one but we would need to keep compatibility with existing popular_enabled parameter.

@SamantazFox advice on my comment please: https://github.com/iv-org/invidious/pull/4674#issuecomment-2118875288

> but for better use - need upload chart in anyone helm repo. we use private nexus. How in there - dont now. Need research You can publish a helm...

We should have a github actions that automatically refresh the list every day.

I'm not fond to clutter too much redirect.invidious.io but you can already get the speed of instances like explained here: https://github.com/iv-org/instances-api/issues/32#issuecomment-2080229672

Related: https://github.com/juanfont/headscale/issues/1545