Add hapi-fhir service to docker-compose.yml

[medchedli]

This pull request adds the hapi-fhir service to the docker-compose.yml file. The hapi-fhir service is configured with the image "jembi/hapi:v7.0.3-wget" and is exposed on port 8081. It is also added to the "smart-health-links-portal-network" network and has a volume mounted for data persistence.

Summary by CodeRabbit

• New Features

  • Introduced a new service, hapi-fhir, enhancing the application's capabilities.
  • The service is now accessible via port 3447 on the host.

• Improvements

  • Implemented a health check for the hapi-fhir service to ensure reliability.

[coderabbitai]

Warning

Rate limit exceeded

@medchedli has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 1 minutes and 37 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between e3208e4 and ec0f8ec.

Walkthrough

A new service named hapi-fhir has been added to the docker-compose.yml file. This service is configured to use a specific Docker image, expose a port, and connect to an existing network. It includes a volume for data storage, several environment variables, and a health check to monitor its availability. The network configuration remains unchanged.

Changes

File	Change Summary
docker-compose.yml	Added new service hapi-fhir with specified image, port mapping, network connection, volume, environment variables, and health check.

Possibly related PRs

• Fix production build #72: Although this PR focuses on the Dockerfile for a Node.js application, it does not directly relate to the changes made in the docker-compose.yml file for the hapi-fhir service, as it does not involve modifications to the same files or services.

Poem

In a world of code, a rabbit hops,
With hapi-fhir, the service pops!
Ports mapped and data stored,
Health checks run, never ignored.
In the network, it finds its place,
A joyful leap in the coding space! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2f6c3d1 and e3208e4.

Files selected for processing (1)

• docker-compose.yml (1 hunks)

Additional context used

yamllint

docker-compose.yml

[error] 81-81: duplication of key "image" in mapping

(key-duplicates)

---

[error] 82-82: duplication of key "ports" in mapping

(key-duplicates)

---

[error] 84-84: duplication of key "networks" in mapping

(key-duplicates)

---

[error] 86-86: duplication of key "volumes" in mapping

(key-duplicates)

---

[error] 88-88: duplication of key "healthcheck" in mapping

(key-duplicates)

Additional comments not posted (1)

docker-compose.yml (1)

64-80: LGTM! The addition of the hapi-fhir service looks good.

The configuration of the hapi-fhir service aligns with the PR objective and includes the necessary settings such as image, port mapping, network, volume, environment variables, and health check.

The past review comment about adding the flag to enable IPS within the instance has been addressed by setting the HAPI_FHIR_IPS_ENABLED environment variable to true.

[yassinedorbozgithub]

LGTM 👍