Closed falko100 closed 4 days ago
@charlesBochet WDYT?
@falko100 @Bonapara Happy to review a PR to add it to environment variables and leverage it in the code :) Looks a legit feature
Hey @charlesBochet , @Bonapara hope everything fine .
It looks quite straight forward to do by adding REDIS_USERNAME and and REDIS_PASSWORD as var env and manage them in [ cache-storage.module-factory, message-queue.module-factory, .env ]
I can work on it if needed
@borel sure, go ahead! I'm happy to review and merge the PR as part of 0.24
Hello @borel,
Are you working on it ?
hey @BalanaguYashwanth , hope you well . Yes i am .
@borel Didn;t understand
Are you still on it @borel? Thanks for contributing
Hey @Bonapara , i started to contribute on it but i will probably don't have time in the coming days :(
is anyone working on this? I want to work on it. May I ?
I think you can work on it, @DurgaManikantaSai, either starting from scratch or using @borel's draft!
Thank you for contributing :)
@Bonapara I am working on It. Thanks
@Bonapara I think some one known as @Weiko fixed this from @borel's draft. Should I have to leave this and search for some other suitable issues ?
@Weiko should we close it?
Yes, this has been solved.
Currently only REDIS_HOST and REDIS_PORT are available within the .env settings. If we want to use a managed redis cluster for our self-hosted twenty, we need to enter a password.