Skip to content

Conversation

@codingbox2022
Copy link
Contributor

@codingbox2022 codingbox2022 commented Aug 30, 2025

Summary by Sourcery

Update and refactor docker-compose configuration to version 3.8, unify service naming, externalize network configuration, and centralize environment settings

Enhancements:

  • Upgrade docker-compose file to version 3.8
  • Standardize service names and container names for API, Redis, and Postgres
  • Bind API port to localhost and replace explicit port mappings with exposes
  • Move Postgres credentials and database settings to environment variables in .env
  • Add restart policies for Redis and ensure services depend on the renamed Postgres service
  • Attach all services to the external dokploy-network with service aliases

@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Aug 30, 2025

Reviewer's Guide

Bumps Docker Compose version to 3.8 and refactors all service definitions to standardize names, networking, port handling and environment variable usage.

File-Level Changes

Change Details Files
Updated Docker Compose version and formatting
  • Bumped compose version to "3.8"
  • Inserted blank lines for readability
docker-compose.yaml
Reconfigured API service networking and dependencies
  • Renamed dependency from postgres to evolution-postgres
  • Restricted port binding to localhost
  • Added dokploy-network
  • Quoted port and expose values
docker-compose.yaml
Standardized Redis service settings
  • Added container_name and restart policy
  • Moved from ports to expose
  • Joined evolution-net and dokploy-network with aliases
docker-compose.yaml
Refactored Postgres service to externalize env vars and networking
  • Renamed service and container_name to evolution-postgres
  • Externalized credentials via .env file
  • Switched command to list syntax
  • Connected service to both networks and set expose
docker-compose.yaml
Added external dokploy-network
  • Declared dokploy-network as external
  • Attached all services to dokploy-network
docker-compose.yaml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey there - I've reviewed your changes - here's some feedback:

  • Binding the API’s port to 127.0.0.1 will prevent external access—confirm if that’s intended or consider using 0.0.0.0 or removing the host address.
  • Since dokploy-network is marked external, ensure its creation process or documentation is updated so deployments won’t fail due to a missing network.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Binding the API’s port to 127.0.0.1 will prevent external access—confirm if that’s intended or consider using 0.0.0.0 or removing the host address.
- Since dokploy-network is marked external, ensure its creation process or documentation is updated so deployments won’t fail due to a missing network.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@DavidsonGomes DavidsonGomes changed the base branch from main to develop September 1, 2025 13:47
@DavidsonGomes DavidsonGomes merged commit a91a4ad into EvolutionAPI:develop Sep 1, 2025
1 check passed
@lotto645sandeepkumar-sys

Bicxucu

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.

3 participants