🔧 Added Doppler to Docker API Image

[rflihxyz]

Summary by CodeRabbit

• New Features

  • Added an environment variable DOPPLER_TOKEN for enhanced configuration management.
  • Changed port mapping for a service to improve accessibility and compatibility.

• Refactor

  • Simplified backend launch command in development and production environments.
  • Updated service environment configurations to streamline deployment processes.

• Chores

  • Removed service dependency checking configuration to optimize startup.

• Bug Fixes

  • Corrected environment variable naming to ensure consistency across platforms.

• Documentation

  • Updated workflow triggers to focus on main branch updates, enhancing CI/CD process efficiency.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d78ce57

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The changes encompass refining Docker configurations and Dockerfile setups across services to enhance environment management. These updates include introducing new environment variables, adjusting port mappings, and simplifying commands to streamline operations and improve integration with the Doppler service for secure environment handling.

Changes

Files	Change Summary
docker-compose.dev.yml	Removed service dependency checking configuration.
docker-compose.source.yml	Added DOPPLER_TOKEN, changed port mapping from 80:3000 to 80:8090, updated argument to VITE_BACKEND_DOMAIN.
packages/api/Dockerfile	Updated context directory to /app/packages/api, simplified launch command, added Doppler CLI installation, and required DOPPLER_TOKEN for environment variable injection.
.github/workflows/docker.export.frontend.selfhosted.yml	Removed pull_request trigger, focusing workflow on push events to the main branch.

Poem

🐇✨
In the realm of bits and Docker's might,
Changes twirl, bringing delight.
Ports shift, tokens gleam anew,
Commands ease, dependencies bid adieu.
On paths we tread, smoother they wind,
For seamless runs and peace of mind. 🌙
🐇✨

---

Recent Review Details

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between bd1d2b6 and d78ce57.

Files selected for processing (1)

• .github/workflows/docker.export.frontend.selfhosted.yml (1 hunks)

Additional comments not posted (2)

.github/workflows/docker.export.frontend.selfhosted.yml (2)

4-6: The workflow is now triggered only on push events to the main branch. This change simplifies the triggering mechanism but consider the potential impact on testing changes before they are merged into the main branch. It might be beneficial to keep the pull_request trigger for running tests or builds on PRs to catch issues early.

---

4-9: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [8-36]

The steps for building and pushing Docker images are well-configured and use appropriate actions and secrets. This setup ensures that the Docker images are built with the necessary environment-specific configurations and are pushed to DockerHub securely.

---

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