Skip to content

Conversation

@anitacaron
Copy link
Collaborator

@anitacaron anitacaron commented Jun 15, 2025

The aim with the Dockerfile is to easily update OBO Dashboard in different repositories (NOR, dashboard template and the OBO Dashboard itself) and not to be dependent on the ODK docker build.

Summary by CodeRabbit

  • Chores
    • Introduced a new Docker image with updated dependencies and Python packages.
    • Simplified the container run command in the script to use the new Docker image.
    • Added support for building and pushing multi-architecture Docker images.
    • Provided a new command-line script to streamline dashboard execution.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 15, 2025

📝 Walkthrough

"""

Walkthrough

A new Dockerfile is introduced that builds an image based on obolibrary/robot:v1.9.8, installing system and Python dependencies and copying project files. The odk.sh script is updated to run the new anitacaron/obo-dashboard image with a simplified Docker run command and fewer volume mounts; the previous obolibrary/odkfull invocation is commented out. A new Makefile target build-docker-v% is added to build and push multi-architecture Docker images. A new executable Bash script obodash is added to run a Python dashboard configuration script inside the container.

Changes

File(s) Change Summary
Dockerfile Added new Dockerfile to build a custom image with system packages, Python dependencies, and source code.
odk.sh Modified Docker run command to use anitacaron/obo-dashboard image with fewer volume mounts; old command commented out.
Makefile Added new target build-docker-v% to build and push multi-architecture Docker images using Docker Buildx.
obodash Added new executable Bash script to run Python dashboard configuration script with arguments inside /tools dir.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant odk.sh
    participant Docker
    participant obo-dashboard (Container)

    User->>odk.sh: Execute script
    odk.sh->>Docker: Run anitacaron/obo-dashboard image (single config volume)
    Docker->>obo-dashboard (Container): Start container with /tools as working directory
    obo-dashboard (Container)-->>User: Executes dashboard logic
Loading

"""


📜 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 b6d1d2a and a38b2b1.

📒 Files selected for processing (4)
  • Dockerfile (1 hunks)
  • Makefile (1 hunks)
  • obodash (1 hunks)
  • odk.sh (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • obodash
  • Makefile
🚧 Files skipped from review as they are similar to previous changes (2)
  • Dockerfile
  • odk.sh
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: QC
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment
  • Commit Unit Tests in branch dockerfile-obodashboard

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this 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.

@anitacaron anitacaron requested a review from matentzn June 15, 2025 20:19
@anitacaron anitacaron self-assigned this Jun 15, 2025
Copy link
Contributor

@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

🧹 Nitpick comments (3)
Dockerfile (2)

1-4: Pin the base image to a specific version for reproducibility.

Using obolibrary/robot:latest may introduce breaking changes when the image is updated. Pin to a known working tag (e.g., obolibrary/robot:1.7.0) to ensure consistent builds.


6-13: Minimize image size by disabling recommended packages.

Add --no-install-recommends to the apt-get install command to avoid pulling in unnecessary packages, and consider combining clean-up steps:

-RUN apt-get update && \
-    apt-get install -y git \
+RUN apt-get update && \
+    apt-get install -y --no-install-recommends git \
         python3 \
         python3-pip \
         python3-venv \
         python-is-python3 \
         jq && \
     rm -rf /var/lib/apt/lists/*
odk.sh (1)

12-17: Remove obsolete commented-out invocation.

The block for obolibrary/odkfull is no longer needed and adds noise. Delete these lines to keep the script concise.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 478c6f8 and 365f461.

📒 Files selected for processing (2)
  • Dockerfile (1 hunks)
  • odk.sh (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: QC
🔇 Additional comments (1)
odk.sh (1)

19-22: Verify that omitting volume mounts fits your workflow.

With no mounts, changes to host files won’t reflect in the container at runtime. Ensure that baking the code and configuration into the image meets your development and deployment needs.

Copy only requirements.txt before installing to avoid reinstalling dependencies on every source change

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@anitacaron anitacaron merged commit d58e537 into master Jun 28, 2025
2 checks passed
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.

2 participants