#Redis

Bon ... 🤬 y a des fedigens sous Debian 12 qui ont installer Valkey qui est censé d'après leur doc être dans les dépôts ​​

#Valkey #Redis #Debian

Vorgestern hatte jemand, ich glaube Du, @galileo , darauf aufmerksam gemacht, dass Mastodon in Version 4.4.0 erschienen ist und man das aktualisieren sollte.

Es war 21:30 Uhr.

Eigentlich wollte ich ins Bett. Aber, ach was solls, installierste mal schnell noch 4.4.0. Oh, mein Ruby und /oder Redis ist jetzt zu alt. Na dann das zu erst.

2:25 Uhr bin ich mit völlig zerschossenem Mastodon ins Bett gefallen.

Und habe mich an meine Regel erinnert: "Mal eben schnell gibt es nicht!"

Am nächsten Morgen habe ich zusammen mit Gemini versucht, das System zum laufen zu bekommen. Wir haben installiert, deinstalliert, wieder installiert, aktiviert und deaktiviert. Wir haben Mastodon komplett sauber neu installiert und wieder deinstalliert. Alles verbunden mit Wartezeiten von durchaus 20 min oder mehr. Irgendwann hat Gemini gemeint: Sorry, ich bin am Ende meines Lateins.

Ich hätte 2 Möglichkeiten:

1. einen "richtigen" Experten mal auf mein System schauen lassen, das Problem liegt offensichtlich ausserhalb von Mastodon
oder
2. Mach Linux platt, installiere es komplett sauber, richte Mastodon neu ein, spiele ein Backup der Userdaten zurück.

Und da waren wir an dem Punkt, den ich immer befürchtet hatte: Ein Backup musste eingespielt werden.

Aber real gesehen war es egal. Die aktuelle Version werde ich nicht mehr hinbekommen. Also habe ich das mittlerweile knapp 3 Jahre alte System gebackupt, es waren am Ende drei Dateien: Datenbank, Medienarchiv, Konfiguration.

Dann habe ich die Platte abgezogen, eine zweite Platte genommen, das System sauber installiert und mit Gemini Schritt für Schritt Mastodon neu eingespielt.

Kritisch war erst ein mal nur der Bereich, die SSL-Verschlüsselung wieder zu aktivieren und dem Webserver zu überzeugen, die richtigen Dateien an der richtigen Stelle auszuspielen.

Und dann war das System, niegelnagelneu, tatsächlich wieder da.

Dann ging es ans Rückspielen. Und was soll ich sagen, es war am Ende tatsächlich relativ simpel. Klar, ohne Gemini hätte ich das nie hinbekommen.

Ich hab Gemini dann drei Listen erzeugen lassen:

1. Den kompletten am Ende funktionierenden Ablauf der Installation
2. Den kompletten am Ende funktionierenden Backup-Prozess.

Und die EISERNE Regel: "MAL SCHNELL GIBT ES NICHT!"

Nach 18 h lief das System wieder (inkl. 4,5 h schlafen).

Ein paar kleinere Dinge, Zeichenlimit, Upload-Limit hab ich dann später noch nachgeführt.

#mastodon #irrfahrt #gemini #linux #ruby #redis #update #backup #restore

Wow, that's annoying, if you open an account with Redis Cloud (redis's hosted service), then you can't self-close it, and instead need to file support ticket to get them to delete your data.

#Redis #RedisCloud

I am back to Redis!
`Redis is now available under the AGPLv3 open source license.`
https://redis.io/blog/agplv3/
#agpl3 #gpl #redis

Fool me once. You can't fool me twice. I'm now using Valkey everywhere. Redis is trying to go back to an open source license.... Little too late now.

https://redis.io/blog/agplv3/

#redis #valkey #Opensource

Redis 8 发布；支持 RSALv2/SSPLv1/AGPLv3 授权三选一。

这也意味着 Redis 8 重新成为使用 OSI 认证开源协议的开源软件。

https://redis.io/blog/agplv3/

thread: /4480

#Redis #Opensource

Telegram 原文

Redis 8 发布；支持 RSALv2/SSPLv1/AGPLv3 授权三选一。

这也意味着 Redis 8 重新成为使用 OSI 认证开源协议的开源软件。

https://redis.io/blog/agplv3/

thread: /4480

#Redis #Opensource

Telegram 原文

Pleased to see #Redis returning to an #OpenSource license.

https://redis.io/blog/agplv3/

Redis is open source again

https://antirez.com/news/151

#redis

#Redis is open source again.

https://antirez.com/news/151

Valkey to replace Redis in the [extra] Repository

https://archlinux.org/news/valkey-to-replace-redis-in-the-extra-repository/

#ArchLinux #Redis #Valkey #Linux

Latest grievance: The #Quarkus Cache guide says `null` will be cached (negative caching) but this is in fact only supported by the default provider (using the great Caffeine library for in-memory cache) but *it is not supported* by any other provider, such as #Redis. 🙃

https://quarkus.io/guides/cache#negative-cache
https://quarkus.io/extensions/io.quarkus/quarkus-redis-cache/
https://github.com/quarkusio/quarkus/issues/39547
https://github.com/quarkusio/quarkus/discussions/42940

Latest grievance: The #Quarkus Cache guide says `null` will be cached (negative caching) but this is in fact only supported by the default provider (using the great Caffeine library for in-memory cache) but *it is not supported* by any other provider, such as #Redis. 🙃

https://quarkus.io/guides/cache#negative-cache
https://quarkus.io/extensions/io.quarkus/quarkus-redis-cache/
https://github.com/quarkusio/quarkus/issues/39547
https://github.com/quarkusio/quarkus/discussions/42940

At this point I'm contemplating rewriting this small #Quarkus application in #SpringBoot.

Every step on the way I'm running into some unsupported things.

Latest frustration: The Quarkus #Redis extension (based on Vert.x Redis 4.x) doesn't support Amazon #IAM. This will be supported in version 5. 🙃

While at the same time there's an official example from #AWS for Lettuce (which #SpringData Redis is based on).

https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/auth-iam.html

✅ Done: Migration from #Redis to #Redict for caches
⏳ In Progress: Migration from MariaDB to Galera Cluster

We were still struggling with email delivery from Forgejo. It looks like some queues are corrupted and restoring them is very hard. Most queued messages are spam or registration emails with already expired tokens. Finally, we made the decision to reset the queue and will do that in a few minutes.

We are using the opportunity to switch the queues to #redict / #redis, which was a planned project anyway (a requirement for clustering our Forgejo to multiple instances).

【図解解説/初心者OK】Next.jsとHonoで爆速タイピングゲームを作ろう【Redis/Bun/TypeScript/Upstash/TailwindCSS】
https://qiita.com/Sicut_study/items/c12faaf962646bee34f7?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #Redis #TypeScript #Next_js #Hono

Can you have a #Pixelfed and #Mastodon in the same server?

I'm seeing very weird things.

1. Some Mastodon lists have 0 posts right now, refreshed and gone.

2. Following a Pixelfed user from Mastodon seems to have no effect.

All systems in Pixelfed and Mastodon seem up.

Could there be a conflict with #Redis or similar?

#MastoAdmin

Redis + Ratatui = 🔥

🧰 **ratisui**: A TUI for exploring Redis databases from the terminal!

🚀 Supports command execution, auto completion, logging & more!

🦀 Written in Rust & built with @ratatui_rs

⭐ GitHub: https://github.com/honhimW/ratisui

#rustlang #ratatui #tui #redis #database #terminal #explore #tool #commandline

The corporation behind #Redis is now starting to chase #OpenSource client libraries claiming trademark violations https://github.com/redis-rs/redis-rs/issues/1419 and are attempting to have the projects transferred to them.

If it wasn't obvious before, now is a good time to fuck the hell off from that software. Just use #Valkey or one of the other alternatives.

#Redis : Destroys their reputation with a shady license change

Community: Moves to #Valkey fork

Redis: It is the people that are wrong, we'll use trademark to control the ecosystem

Result:

https://github.com/redis-rs/redis-rs/issues/1419

#rust #rustlang

Rearchitecting: #Redis to #SQLite
https://wafris.org/blog/rearchitecting-for-sqlite

Wafris' migrated from #Redis to #SQLite for its Rails middleware client. SQLite outperformed Redis in its specific use case, offering about 3x speed improvement locally.

https://wafris.org/blog/rearchitecting-for-sqlite

#Hollo now can work without #Redis. It uses Redis as a cache and queue backend if the REDIS_URL environment variable is provided, but if not given, it caches in memory and works without a queue. This is an option to consider if you have a few following/followers.

I've migrated Redis to KeyDB and separated the volatile cache from Sidekiq jobs and Mastodon timelines. While this might not result in a performance boost due to the low load, it will enable some exciting new features (spoiler: KeyDB supports master-master replication).

Stay tuned!

#Redis #KeyDB #Mastodon #Sidekiq #BSDCafe #BSDCafeServices #BSDCafeUpdates

Sentry is hiring Senior Software Engineer, Platform

🔧 #golang #python #rust #django #kafka #postgresql #redis #seniorengineer
🌎 Toronto, Canada
⏰ Full-time
🏢 Sentry

Job details https://jobsfordevelopers.com/jobs/senior-software-engineer-platform-at-sentry-io-feb-22-2024-9c4dd4?utm_source=mastodon.world&utm_medium=social&utm_campaign=posting
#jobalert #jobsearch #hiring

#Fedify has supported optional queuing for outgoing activities, with two built-in message queue backends: InProcessMessageQueue, which is suitable for development, and DenoKvMessageQueue, which is only available in Deno.

Fedify has also had two built-in cache backends, MemoryKvStore, which is suitable for development, and DenoKvStore, which is only available in Deno.

Now, however, by installing the @fedify/redis package, you can use #Redis as both a message queue backend and a cache backend! Unlike DenoKvMessageQueue and DenoKvStore, it's also available for #Node.js and #Bun.

This feature was made possible with the support of @ghost.

https://github.com/dahlia/fedify-redis

#fedidev