Literally could use an LLM to find answers, it doesn’t get any easier

[ Removed by Reddit ]

Finding these answers would be good first steps, if you don't want to do the research for that you should not go further.
Trial and error is what makes you improve, not asking others.

don't do it.

thanks. the pitch is for cloud-native / devops / DBA / platform teams who already live in DBeaver or DataGrip - no sharing those client passwords around, no extra desktop install. one browser UI instead of pgAdmin + phpMyAdmin + a mongo client + redis-cli.

you're right that Redis is the thin part of that. web UIs for it are scarce, and that's the gap we want to close - being on redis.io is the biggest reason this stays a priority.

Valkey (plus Dragonfly, KeyDB, Garnet) already go through the Redis driver. Memurai isn't on that list yet. good call, we'll add it as a target.

Being the only third-party tool listed there is pretty cool. Since LibreDB Studio is positioning itself as a broad database UI rather than a Redis-only tool, compatibility testing matters a lot. Memurai could be one useful Redis-compatible target to include alongside Redis and Valkey.

Idk.one person asked me to create them, so I wonder if anyone else would be interested. It takes a lot of work so makes no sense to do it for one person

Hum... No ? Why ?

Stupid.

I actually solved that 10 minutes later, got your hint btw thanks

Nobody can help you with what you've given us but it might help you to learn how to read an error message. Lots of hints in there.

u/pulsecron I like the direction of your app, but it has some really annoying bugs.

1. If I search for a key, it appears in the left pane, but disappears as soon as I click on it to expand details.

2. I can't expand the tree preview of a nested json field. When hover/click over the value, a popup with a json tree preview appears but disappears right away.

Would really appreciate if you could resolve them 😢

It's source available. If TCO is more important to you than ideals, or you want to run on k8s it should be in the running. I don't see open source listed as a requirement.

Given the whole Redis debacle I'm surprised you'd even bring this up.

If you contribute to open source and follow what hyperscalers do you can't afford to license things the way we'd like.

Does it support my usecase?

Not open source

Check out Dragonfly DB. We're very happy with it. If your on kubernetes the operator is pretty handy.

A lot of counter bugs come from treating Redis like a variable in app memory. Two workers can both read the same value with GET, both add one, and then both write back the same result. With Redis-compatible servers like Memurai, the safer pattern is still INCR, or Lua/transactions when the logic needs more than one command.

I am pretty sure the usage of databases in redis is discouraged in its own documentation, prefixing is really the way to go.

just open redis.conf and change/add line
> databases 16

🫣

The primary way of doing this is with name spacing, like each app always uses a certain prefix for their keys, distinct from other apps.

I don't disagree with any of this, just wanted to figure out if its possible or if there is a solution to use a single instance with multiple apps, at least in a homelab env

I recommend figuring out how to streamline each application getting its own redis instance. Redis is super tiny, so target low overhead in that goal. As each application scales you'll want a way to tune redis parameters to match those needs. By coupling it all together often those knob values end up conflicting. Some apps may be more CPU intensive, some more ram. Some may be more tolerant of latency spikes, like when a big SINTERSTORE needs to be done, while others don't.

Since you were ok with different databases you don't sound like you need to share key space with other apps, which further supports partitioning different redis instances to each app.

I believe the 16 databases in redis was kind of a mistake … that’s what I heard before.

Now Redis is fantastic. This is what you can do:
1. Prefix the keys to belong to whatever thing it is . IE customers:id:123456.
2. The hard part - have other instances and use the 16dbs in each.

But hey, good luck. Someone else may have a better solution.

Can you please elaborate? Also I am looking for a no cost solution since this is for my homelab. I am not sure if this would fit that

redis enterprise :-)