| Time |
Nick |
Message |
| 00:36 |
|
collum joined #evergreen |
| 01:37 |
|
collum joined #evergreen |
| 02:37 |
|
collum joined #evergreen |
| 03:38 |
|
collum joined #evergreen |
| 04:39 |
|
collum joined #evergreen |
| 05:40 |
|
collum joined #evergreen |
| 06:40 |
|
collum joined #evergreen |
| 09:32 |
|
sandbergja joined #evergreen |
| 10:44 |
|
Dyrcona joined #evergreen |
| 11:37 |
|
jihpringle joined #evergreen |
| 14:01 |
|
jihpringle joined #evergreen |
| 14:36 |
eeevil |
berick: I'm close to a branch on opensrf+redis, but do you have a minute for a question that may keep me from going down a cul de sac you've explored already? |
| 14:36 |
berick |
eeevil: yes |
| 14:38 |
eeevil |
rock. so, is there a reason I'm not seeing for having the redis user setup (bus reset, etc) in a text file, rather than just generating the redis commands in the perl and feeding them into either a redis CLI subcommand, or (better IMO) using Redis.pm (or, maybe we can use Redis::Fast?) instance? |
| 14:39 |
eeevil |
all the info, save the "default" user's password, seems to be in opensrf_core.xml, no? |
| 14:39 |
eeevil |
I'm looking to remove one more place for typos and thinkos to creep in |
| 14:41 |
berick |
early on something about the visibility of a standalone file of accounts was appealing. i'm sure the perl approach would work fine thought |
| 14:42 |
eeevil |
ok, thanks. I wanted to make sure there wasn't some redis requirement I wasn't grok'ing ... like how /etc/sudoers can't be a symlink |
| 14:42 |
berick |
nah |
| 14:45 |
eeevil |
relatedly, have I missed any further discussion on support of a particular redis-proper replacement, like valkey, etc? (hint: I'm currently in favor of valkey ...) |
| 14:54 |
berick |
valkey is the assumed replacement, at least last it was discussed. i think we're just watiing for packages to be generally available |
| 14:54 |
berick |
(they may be by now) |
| 16:05 |
|
jihpringle joined #evergreen |
| 16:56 |
jeff |
Valkey has been looking like the most popular / healthy alternative, with lots of backing... also, in the meantime, antirez returned to Redis and they appear to have switched from the (unpopular, fork-inciting) SSPL license to AGPL. |
| 16:56 |
jeff |
oh, and I see I failed to hit enter earlier and berick has answered in the meantime. :-) |
| 16:58 |
jeff |
Valkey packages are in testing (trixie) and in stable-backports (bookworm-backports): https://tracker.debian.org/pkg/valkey |
