Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Download ddev images during prebuild #148

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

shaal
Copy link
Owner

@shaal shaal commented Apr 23, 2024

Summary by CodeRabbit

  • New Features
    • Enhanced the development environment setup with commands for downloading debugging images and initiating the ddev environment.

@shaal shaal self-assigned this Apr 23, 2024
Copy link

codesandbox bot commented Apr 23, 2024

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

Copy link
Contributor

coderabbitai bot commented Apr 23, 2024

Walkthrough

This update introduces enhancements to the development setup by incorporating commands to download necessary images for debugging and initiating the ddev environment. These additions streamline the process, making it easier for developers to set up and debug projects efficiently.

Changes

File Path Change Summary
.gitpod/utils/.../ddev-in-gitpod-setup.sh Added commands for downloading images and starting the ddev environment.

🐰✨
In the burrow of code, deep and wide,
A rabbit hops with a joyful stride.
Images fetched, the environment's set,
Debugging's a breeze, no need to fret!
Hoppity hop, on code we dine, tonight! 🌟


Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 8ddc8c9 and 954aeff.
Files selected for processing (1)
  • .gitpod/utils/ddev-in-gitpod-setup.sh (1 hunks)

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
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

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

Comment on lines +8 to +9
time ddev debug download-images
time ddev start
Copy link
Contributor

Choose a reason for hiding this comment

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

Consider adding error handling for the ddev commands.

It's important to ensure that the script handles potential errors gracefully. You might want to add checks to see if the commands succeed and provide appropriate error messages or recovery mechanisms if they fail. For example:

if ! time ddev debug download-images; then
    echo "Failed to download ddev images."
    exit 1
fi
if ! time ddev start; then
    echo "Failed to start ddev."
    exit 1
fi

@@ -5,3 +5,5 @@ fi

# Misc housekeeping before start
ddev config global --instrumentation-opt-in=true
time ddev debug download-images
Copy link

Choose a reason for hiding this comment

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

Why do this if you're going to do a ddev start anyway?

And (not sure of context) why is the ddev start there? Is it a bogus start?

Copy link
Owner Author

Choose a reason for hiding this comment

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

I tried just downloading using ddev debug function. But later when I ran ddev start it decided to download more thighs that were not download previously. ddev start - ensure that I get all the images (during prebuild)

Copy link

Choose a reason for hiding this comment

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

But in that case the ddev debug download-images is not useful, true?

Also, the last time we tried this the images didn't persist anyway. I hope they're persisting now?

Note that ddev start will get the specified database type/version, whereas ddev debug download-images will get the default. In our current world, these should be the same, mariadb:10.11

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.

None yet

2 participants