chore: change redis container name

[Raj-G07]

Closes #407

Summary by CodeRabbit

• Chores
  • Updated the Redis container’s name to “nixopus-redis” for consistent identification across environments.
  • No changes to ports, volumes, health checks, or networking; existing connections and data remain unaffected.
  • Users who interact with the container by name (e.g., via docker exec, logs, or tooling) should use the new container name.
  • Automation or scripts referencing the previous container name may need to be adjusted to reflect this update.

[coderabbitai]

Walkthrough

Renamed the docker-compose service nixopus-redis container_name from nixopus-redis-container to nixopus-redis. No other changes.

Changes

Cohort / File(s)	Summary of Changes
Docker Compose Config docker-compose.yml	Updated service nixopus-redis property container_name: nixopus-redis-container → nixopus-redis.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• feat: add redis service in docker compose #386 — Adjusts the same nixopus-redis service container_name, directly related to this rename.

Suggested labels

nixopus-docker

Suggested reviewers

• raghavyuva

Poem

I nudge a name, hop-hop—so neat,
From long to short, a tidy feat.
Compose now calls the Redis pod,
By nixopus-redis—give a nod.
Ears up, config set, I thump with glee,
A tiny change, as clean as can be. 🐇✨

✨ Finishing touches

🧪 Generate unit tests

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

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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.}

Pre-merge checks

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues Check	✅ Passed	The changeset updates docker-compose.yml by changing the container_name from "nixopus-redis-container" to "nixopus-redis", which directly implements the objective of linked issue #407 and aligns with the PR description "Closes #407".
Out of Scope Changes Check	✅ Passed	Based on the provided summary, the only modification is the container_name change in docker-compose.yml and there are no other file or service changes, so I find no out-of-scope changes unrelated to issue #407.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Title Check	✅ Passed	The title "chore: change redis container name" succinctly and accurately describes the primary change in this PR — renaming the Redis container in docker-compose.yml. It is concise, uses a conventional "chore:" prefix, and directly maps to the linked issue objective. This makes the intent clear to reviewers and history scanners.

[zhravan]

That was fast!

PR LGTM 💚

Good work!

[Raj-G07]

@zhravan Hi , I am participant of hactoberfest 2025 , if this PR count can we close and merge it after 1st Oct

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

docker-compose.yml (3)

63-74: Add a temporary network alias to preserve backward compatibility.

If any scripts/configs were reaching Redis via the old hostname nixopus-redis-container, add it as a transient alias to avoid breakage during rollout. Remove the alias after dependents migrate.

   nixopus-redis:
     image: redis:7-alpine
     container_name: nixopus-redis
     restart: unless-stopped
@@
-    networks:
-      - nixopus-network
+    networks:
+      nixopus-network:
+        aliases:
+          - nixopus-redis
+          - nixopus-redis-container  # TODO: drop after clients migrate

---

63-75: Deployment note: clean up the old container after rename.

On existing hosts, run docker compose down --remove-orphans before bringing the stack up to avoid stale containers lingering under the old name.

---

65-65: Future clean-up: consider dropping container_name entirely.

Relying on the service name (nixopus-redis) improves DNS consistency and supports scaling. Keep the current change to close #407; consider this in a follow-up.

-    container_name: nixopus-redis
+    # container_name intentionally omitted; use service DNS name "nixopus-redis"

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6777ca8 and d78ed3b.

📒 Files selected for processing (1)

• docker-compose.yml (1 hunks)

🔇 Additional comments (2)

docker-compose.yml (2)

65-65: LGTM — rename matches Issue #407.

The container_name is correctly updated to nixopus-redis as requested.

---

65-65: Verify & update references to old Redis container name "nixopus-redis-container"

I couldn't scan the repo (ripgrep: "No files were searched"); manually confirm no scripts, compose overrides, CI jobs, or docs reference "nixopus-redis-container". Current change: docker-compose.yml (line 65) sets container_name: nixopus-redis.

[zhravan]

@zhravan Hi , I am participant of hactoberfest 2025 , if this PR count can we close and merge it after 1st Oct

@Raj-G07 : for now, please dont worry too much about it, we will have more beginner-friendly issues coming up during Hacktoberfest, and this work can serve as a great learning and preparation step towards those.

We will definitely have more issues for you to contribute once the event kicks off. I hope that sounds okay.

We have 15 days more, keeping PR stale wouldn't be good. I will suggest continue picking up issues you like to work on, this will help you build a foundation on project.

We are always here to guide you to contribute and learn together.

Also, we have exciting collabs/activities coming soon for Hacktoberfest event, stay tuned on to our Discord channel.

[Raj-G07]

@zhravan Thanks for clarifying! That makes sense. Appreciate all the support and guidance.