Update docker-compose.yaml

[DrinkMoreJuice]

This PR fixes a networking issue where the Redis service was not attached to the shared mosip_network, preventing Mimoto from connecting to Redis.

Redis is required for token caching and issuance-related session management. Because Redis was missing from the shared network, Mimoto could not resolve the hostname redis, resulting in connection errors.

The fix adds the Redis container to the shared network:

redis:
image: redis:alpine
ports:
- "6379:6379" volumes:
- redis-data:/data networks:
- network

With this change, Mimoto is now able to connect to Redis successfully, and the credential issuance flow operates correctly.

Summary by CodeRabbit

• Chores
  • Updated Docker Compose configuration to connect Redis to the external network, improving service communication in containerized deployments.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A networks configuration was added to the Redis service in docker-compose.yaml, connecting it to an external network named "network" for inter-service communication within the Injistack deployment environment.

Changes

Cohort / File(s)	Summary
Docker Compose Network Configuration docker-compose/docker-compose-injistack/docker-compose.yaml	Added networks property to Redis service, connecting it to external network named "network"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single-file configuration change with straightforward network attachment
• No logic modifications or functional impact
• Standard Docker Compose networking syntax

Suggested reviewers

• jackjain
• vishwa-vyom

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update docker-compose.yaml' is vague and generic, using non-descriptive terms that don't convey the specific networking fix being implemented.	Use a more specific title that describes the actual change, such as 'Add Redis service to shared network in docker-compose.yaml' or 'Fix Redis connectivity in docker-compose by adding network configuration'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 618684d and a142c40.

📒 Files selected for processing (1)

• docker-compose/docker-compose-injistack/docker-compose.yaml (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: Piyush7034
Repo: mosip/inji-certify PR: 488
File: docker-compose/docker-compose-injistack/docker-compose.yaml:82-83
Timestamp: 2025-11-03T05:40:24.121Z
Learning: In the mosip/inji-certify repository, hardcoded database credentials in docker-compose files are acceptable when the database runs as a container in the same docker-compose stack for local development/testing purposes.

🔇 Additional comments (1)

docker-compose/docker-compose-injistack/docker-compose.yaml (1)

23-24: Fix is correct: Redis is now discoverable within the shared network.

This change resolves the networking issue by attaching the Redis service to the mosip_network shared network. This allows the Mimoto service (line 80) to resolve the hostname redis and establish connections for token caching and session management. The configuration is consistent with all other services in the compose file (database, certify, certify-nginx, mimoto-service, inji-web), all of which already reference the same network.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[swatigoel]

@DrinkMoreJuice can you please raise PR for develop branch?

[DrinkMoreJuice]

@DrinkMoreJuice can you please raise PR for develop branch?

I’ve updated this pull request to target the develop branch.

[swatigoel]

@DrinkMoreJuice There are so many changes and conflicts in this PR. Looks like you need to raise fresh PR with only docker-compose changes.

[swatigoel]

@DrinkMoreJuice can you please raise fresh PR for develop branch with changes specific to docker-compose only.