feat: add Docker support with multi-stage build, Nginx configuration,…

[kpj2006]

… and Docker Compose orchestration

Addressed Issues:

Fixes #(issue number)

Screenshots/Recordings:

Additional Notes:

Checklist

• My code follows the project's code style and conventions
• I have made corresponding changes to the documentation
• My changes generate no new warnings or errors
• I have joined the Discord server and I will share a link to this PR with the project maintainers there
• I have read the Contributing Guidelines

⚠️ AI Notice - Important!

We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact.

Summary by CodeRabbit

• New Features
  • Added Docker support for running the app in a container.
  • Added a ready-to-use Compose setup with port mapping for local access.
  • Included web server configuration to support direct links and page refreshes.
• Documentation
  • Expanded the getting-started guide with Docker Compose and Docker CLI instructions.
  • Documented the local URL to open the app in a browser.
• Chores
  • Added ignore rules to keep build artifacts and local files out of container builds.

[coderabbitai]

Warning

Review limit reached

@kpj2006, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 34 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5b88afe6-53ea-4e21-b99d-16fcbf7f4876

📥 Commits

Reviewing files that changed from the base of the PR and between 593bba0 and d162282.

📒 Files selected for processing (1)

• Dockerfile

Walkthrough

This PR adds Docker containerization support: a multi-stage Dockerfile building the app with Node and serving it via Nginx, a custom nginx.conf for SPA routing and gzip, a docker-compose.yml service definition, a .dockerignore file, and README documentation for Docker usage.

Changes

Docker Support

Layer / File(s)	Summary
Docker build and nginx serving checkpoint Dockerfile, nginx.conf, .dockerignore	Multi-stage build compiles the app with Node, then Nginx serves the built output using a custom config with SPA fallback, gzip, and error handling; .dockerignore excludes build artifacts and metadata from the build context.
Compose orchestration and docs checkpoint docker-compose.yml, README.md	Defines the orgexplorer service with port mapping and restart policy, and documents Docker Compose/CLI usage in the README.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Sequence Diagram(s)

Not applicable — changes are configuration/documentation additions without multi-component runtime interaction to visualize.

Suggested labels: Documentation

Poem

A hop, a build, a container spins,
Nginx serves where npm begins.
With gzip fast and routes so true,
This bunny ships a Docker stew. 🐰🐳
Onward to port eight-oh-oh-oh!

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: adding Docker support with a multi-stage build and Nginx configuration.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@Dockerfile`:
- Around line 17-27: Add a HEALTHCHECK to the nginx stage in the Dockerfile so
Docker/Compose can verify the container is actually serving HTTP. Update the
final nginx image block that currently contains the COPY, EXPOSE, and CMD
directives to include a lightweight probe against the served site (for example
via localhost) and mark the container unhealthy on failed responses. Keep the
check near the nginx runtime configuration so it’s easy to find alongside the
existing CMD and EXPOSE instructions.

In `@README.md`:
- Around line 319-334: Add blank lines before and after each fenced code block
in the Docker usage sections of README.md to satisfy MD031; update the examples
around the build/run commands so the list items in the Docker Compose and Docker
CLI sections have empty lines surrounding the ```bash fences, keeping the
surrounding numbered steps intact.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 63f98cad-5823-4b92-9646-03d2cc8e19ad

📥 Commits

Reviewing files that changed from the base of the PR and between d904719 and 593bba0.

📒 Files selected for processing (5)

• .dockerignore
• Dockerfile
• README.md
• docker-compose.yml
• nginx.conf