Conversation

Notices

1. Embed this notice
   Francis Augusto 🇳🇴/🇧🇷/:bahia: (francis@mastodon.babb.no)'s status on Thursday, 04-Jan-2024 20:50:51 JST Francis Augusto 🇳🇴/🇧🇷/:bahia:

   • Renaud Chaput

   @renchap I really wish I was using it. I am starting to loose count of how many redis instances I have...

   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Thursday, 04-Jan-2024 20:50:49 JST Renaud Chaput

     in reply to

     @francis You can use Redis databases, it will be more future-proof. I really advise against using namespaces.

   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Thursday, 04-Jan-2024 21:06:35 JST Renaud Chaput

     in reply to

     • Joshix

     @joshix Yes, if you care about your instances being fully isolated from each other, then you need to have at least 1 Redis server per instance. But this is even worse when using namespaces :)
     @francis

   • Embed this notice
     Joshix (joshix@fosspri.de)'s status on Thursday, 04-Jan-2024 21:06:37 JST Joshix

     in reply to

     • Renaud Chaput

     @renchap @francis but there is no database level acl https://github.com/redis/redis/issues/8099

   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Thursday, 04-Jan-2024 21:12:42 JST Renaud Chaput

     in reply to

     • Joshix

     @joshix True, this can work but I dont expect most people to know about this, and implement it. Also we *will* remove namespace/prefix support at some point, there is not much choice here for us.

   • Embed this notice
     Joshix (joshix@fosspri.de)'s status on Thursday, 04-Jan-2024 21:12:43 JST Joshix

     in reply to

     • Renaud Chaput

     @renchap shouldn't prefixes with acl be enough? That should prevent wrong access without running multiple instances