fix: add new env var to docker env

[fmorency]

Summary by CodeRabbit

• Chores
  • Enhanced the GitHub Actions workflow by adding new environment variables for improved Docker build configuration.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request involve the modification of the GitHub Actions workflow defined in the .github/workflows/docker.yml file. Specifically, three new environment variables have been added to the .env file creation step, enhancing the configuration for the Docker build process. The workflow structure and other steps remain unchanged.

Changes

File	Change Summary
.github/workflows/docker.yml	Added three new environment variables to the .env file creation step: NEXT_PUBLIC_MAINNET_EXPLORER_URL, NEXT_PUBLIC_TESTNET_INDEXER_URL, and NEXT_PUBLIC_MAINNET_INDEXER_URL.

Possibly related PRs

• ci: docker testnet #58: The changes in the main PR regarding the addition of new environment variables in the .env file creation step are directly related to the workflow defined in PR ci: docker testnet #58, which also involves creating a .env file and populating it with environment variables necessary for the Docker build process.

Suggested labels

enhancement

Suggested reviewers

• jgryffindor
• chalabi2

Poem

In the land of code, where rabbits play,
New variables hop in, brightening the day.
With Docker's embrace, our builds will soar,
Each line a treasure, who could ask for more?
So let’s celebrate this change with cheer,
For every new line brings us closer, my dear! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 20e0804 and 5b9c399.

📒 Files selected for processing (1)

• .github/workflows/docker.yml (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

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.39%. Comparing base (20e0804) to head (5b9c399).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #106   +/-   ##
=======================================
  Coverage   59.39%   59.39%           
=======================================
  Files         146      146           
  Lines       14389    14389           
=======================================
  Hits         8546     8546           
  Misses       5843     5843           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.