-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removed unused redis
service
#45
Conversation
Service owners can clarify this. Let's wait on this for now. |
@chinmoy12c @pankajjangid05 can you confirm this? Last time I deployed I saw same redis being used to stored and then fetch key-value |
Both transaction layer (SpringBoot services) as well as uci-api is using 6379 for redis cache. |
6379 is going to be common, as we are using internal docker compose network to connect services. hostname is the one which help identify if the cache is same or not. |
A small update, initially I didn't notice that there is another redis instance named |
redis
service
️✅ There are no secrets present in this pull request anymore.If these secrets were true positive and are still valid, we highly recommend you to revoke them. 🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request. |
* Refactor Fusionauth Forms-DB-GQL Admin Key Configuration (#38) * modified hasura-gql-key * Added new enviroment variable for formsdb hasura * Changes (#49) * Minio Fusionauth initial setup * modified kickstart and other changes * removed unused redis service (#45) * Minor fixes * Added manual instructions to readme
* Refactor Fusionauth Forms-DB-GQL Admin Key Configuration (samagra-comms#38) * modified hasura-gql-key * Added new enviroment variable for formsdb hasura * Changes (samagra-comms#49) * Minio Fusionauth initial setup * modified kickstart and other changes * removed unused redis service (samagra-comms#45) * Minor fixes * Added manual instructions to readme
* Refactor Fusionauth Forms-DB-GQL Admin Key Configuration (samagra-comms#38) * modified hasura-gql-key * Added new enviroment variable for formsdb hasura * Changes (samagra-comms#49) * removed unused redis service (samagra-comms#45)
* Refactor Fusionauth Forms-DB-GQL Admin Key Configuration (#38) * modified hasura-gql-key * Added new enviroment variable for formsdb hasura * Changes (#49) * removed unused redis service (#45) * Changed Cassandra image to bitnami (#54) * Changed Cassandra image to bitnami * Removed exposed ports * Adeed host and modified seeds param * Minor change * Added Github token logic (#55) * Using bind mounts instead of docker volumes (#43) * changed volumes to bind mounds * Refactor Fusionauth Forms-DB-GQL Admin Key Configuration (#38) * modified hasura-gql-key * Added new enviroment variable for formsdb hasura * Changed mount points * Minor change * Removed config and socket files from data * Changes (#49) * Fixed mounts for config files and other minor fixes * Unmounted build folder * Fusionauth minio setup (#53) * Refactor Fusionauth Forms-DB-GQL Admin Key Configuration (#38) * modified hasura-gql-key * Added new enviroment variable for formsdb hasura * Changes (#49) * Minio Fusionauth initial setup * modified kickstart and other changes * removed unused redis service (#45) * Minor fixes * Added manual instructions to readme * Dev Sync (#57) * Refactor Fusionauth Forms-DB-GQL Admin Key Configuration (#38) * modified hasura-gql-key * Added new enviroment variable for formsdb hasura * Changes (#49) * removed unused redis service (#45) --------- Co-authored-by: Anvansh <32684077+RyanWalker277@users.noreply.github.com>
Fixes #44
It looks like the
uci-api-scheduler-db
container may not be needed because none of the services use it. However, thecache
container seems to be necessary for theuci-transport-socket
service to work properly. Please let me know, if I am mistaken.