Skip to content

Conversation

@techy4shri
Copy link

@techy4shri techy4shri commented Jan 7, 2026

📋 Description

JIRA ID:

  • Added detailed readme files with troubleshooting common errors, local and mock prod setup and updated setup steps with more generalised edits.
  • Fixed FlyAwayMigration issues when applying migrated data for db.

✅ Type of Change

  • 🐞 Bug fix (non-breaking change which resolves an issue)
  • New feature (non-breaking change which adds functionality)
  • 🔥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 🛠 Refactor (change that is neither a fix nor a new feature)
  • ⚙️ Config change (configuration file or build script updates)
  • 📚 Documentation (updates to docs or readme)
  • 🧪 Tests (adding new or updating existing tests)
  • 🎨 UI/UX (changes that affect the user interface)
  • 🚀 Performance (improves performance)
  • 🧹 Chore (miscellaneous changes that don't modify src or test files)

ℹ️ Additional Information

Please describe how the changes were tested, and include any relevant screenshots, logs, or other information that provides additional context.

Summary by CodeRabbit

  • Documentation
    • Added comprehensive AMRIT-DevOps setup workflow with detailed step-by-step instructions
    • Enhanced troubleshooting section with Docker and database connection diagnostics
    • Included environment configuration and credential setup examples
    • Updated MySQL version specifications to 8.0
    • Improved overall documentation structure and formatting

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

techy4shri and others added 2 commits January 7, 2026 21:07
add: troubleshooting section, proper installation steps
fix: correct typos in usage examples
@coderabbitai
Copy link

coderabbitai bot commented Jan 7, 2026

📝 Walkthrough

Walkthrough

This pull request updates the README.md with comprehensive AMRIT-DevOps setup instructions, including MySQL 8.0 specificity, Docker Desktop guidance, environment configuration details, step-by-step build commands, and an expanded troubleshooting section addressing common setup issues.

Changes

Cohort / File(s) Summary
Documentation & Setup Instructions
README.md
Replaces generic MySQL note with MySQL 8.0.x specificity; adds Docker Desktop note; introduces new "Setup with AMRIT-DevOps" section with multi-step workflow, ASCII flow diagrams, and environment setup commands; expands credentials section with explicit property examples for four databases (db_iemr, db_identity, db_reporting, db_1097_identity); adds Steps 4–6 for building migrations and verification.
Troubleshooting & Issue Resolution
README.md
Reworks Common Issues & Troubleshooting section with five new subsections: Migration Failures (database existence validation), Database Connection Issues (docker diagnostics and MySQL connection testing), Docker Desktop Not Running (connection refused guidance), MySQL Version Compatibility (version check snippet), and First-Time Setup Slow (startup time notes).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Hop through docs with clearer paths,
MySQL eight, no more mishaps,
AMRIT-DevOps setup's now a breeze,
Docker dreams and properties please—
Troubleshooting trails for thee and me! 🛠️✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly relates to the main change—comprehensive README updates with detailed database setup guidelines, troubleshooting sections, and step-by-step instructions.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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

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

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jan 7, 2026

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In @README.md:
- Around line 61-83: The fenced ASCII diagram code block lacks a language
specifier; update the opening fence for the ASCII flow diagram (the
triple/backtick block containing the AMRIT-DevOps / AMRIT-DB steps) to include a
language label such as "text" (e.g., change ``` to ```text) so markdown linters
(MD040) and renderers treat it as a code block with an explicit language.
🧹 Nitpick comments (1)
README.md (1)

57-57: Consider a more concise phrasing.

"in conjunction with" is correct but verbose. Consider shorter alternatives like "works with" or "integrates with" for improved readability.

📝 Proposed revision
-This repository works in conjunction with [AMRIT-DevOps](https://github.com/PSMRI/AMRIT-DevOps) for complete database setup.
+This repository integrates with [AMRIT-DevOps](https://github.com/PSMRI/AMRIT-DevOps) for complete database setup.
📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c2bb4f5 and 51ecd8a.

📒 Files selected for processing (1)
  • README.md
🧰 Additional context used
🪛 LanguageTool
README.md

[style] ~57-~57: ‘in conjunction with’ might be wordy. Consider a shorter alternative.
Context: ...h AMRIT-DevOps This repository works in conjunction with [AMRIT-DevOps](https://github.com/PSMRI...

(EN_WORDINESS_PREMIUM_IN_CONJUNCTION_WITH)

🪛 markdownlint-cli2 (0.18.1)
README.md

61-61: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🔇 Additional comments (3)
README.md (3)

50-51: Excellent version and runtime clarity.

Specifying MySQL 8.0.x and the Docker Desktop dependency prevents common setup failures. This is exactly the level of detail needed for reproducible local environments.


85-134: Comprehensive and actionable setup instructions.

The step-by-step instructions are well-structured with concrete examples for all four databases, clear commands, and appropriate wait-time guidance. This significantly improves the developer experience for first-time setup.


202-222: Well-organized troubleshooting with practical commands.

The expanded troubleshooting section directly addresses common setup pain points with concrete, testable solutions. The version check, Docker verification, and connection test commands are particularly valuable for self-service debugging.

Comment on lines +61 to +83
```
┌─────────────────────────────────────────────────────────────────┐
│ AMRIT-DevOps/amrit-local-setup (or amrit-docker-setup) │
│ 1. docker-compose up -d │
│ 2. Wait 30-60 seconds for MySQL to initialize │
└──────────────────────────────┬──────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────┐
│ AMRIT-DB (this repository) │
│ 3. Configure common_local.properties │
│ 4. mvn clean install -DENV_VAR=local │
│ 5. mvn spring-boot:run -DENV_VAR=local │
│ 6. Wait for migrations to complete, then Ctrl+C │
└──────────────────────────────┬──────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────┐
│ AMRIT-DevOps (return) │
│ 7. Load master data (optional) │
│ 8. Start application services │
└─────────────────────────────────────────────────────────────────┘
```
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Add language specifier to fenced code block.

The ASCII flow diagram is excellent for visualizing the setup workflow, but the code fence is missing a language identifier per markdown linting standards (MD040).

🔧 Proposed fix

Change line 61 from:

to:
```

This allows markdown linters and renderers to properly recognize the block as a code/diagram block.
</details>

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 markdownlint-cli2 (0.18.1)</summary>

61-61: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

</details>

</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

In @README.md around lines 61 - 83, The fenced ASCII diagram code block lacks a
language specifier; update the opening fence for the ASCII flow diagram (the
triple/backtick block containing the AMRIT-DevOps / AMRIT-DB steps) to include a
language label such as "text" (e.g., change totext) so markdown linters
(MD040) and renderers treat it as a code block with an explicit language.


</details>

<!-- fingerprinting:phantom:triton:mongoose -->

<!-- This is an auto-generated comment by CodeRabbit -->

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant