Skip to content

correct evolution api docker image to the latest one and implement missing configuration for the latest features #429

Closed
mrj0b wants to merge 5 commits intoDokploy:canaryfrom
mrj0b:main
Closed

correct evolution api docker image to the latest one and implement missing configuration for the latest features #429
mrj0b wants to merge 5 commits intoDokploy:canaryfrom
mrj0b:main

Conversation

@mrj0b
Copy link
Copy Markdown

@mrj0b mrj0b commented Oct 6, 2025

fix for 428 and 430

@github-actions
Copy link
Copy Markdown

github-actions bot commented Oct 6, 2025

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
templates ✅ Ready (View Log) Visit Preview e71ed7e

@mrj0b
Copy link
Copy Markdown
Author

mrj0b commented Oct 6, 2025

don't merge yet i'll make other changes to implement configurations for all the new features on the latest version to makes them work

@mrj0b mrj0b changed the title correct evolution api docker image to the official one correct evolution api docker image to the latest one Oct 6, 2025
@mrj0b mrj0b changed the title correct evolution api docker image to the latest one correct evolution api docker image to the latest one and implement missing configuration for the latest features Oct 6, 2025
@mrj0b
Copy link
Copy Markdown
Author

mrj0b commented Oct 6, 2025

ready for review and merge

@Harikrishnan1367709
Copy link
Copy Markdown
Contributor

Screenshot 2025-10-07 at 9 01 56 PM Screenshot 2025-10-07 at 9 01 48 PM

Copy link
Copy Markdown
Contributor

@matheusfelipeog matheusfelipeog left a comment

Choose a reason for hiding this comment

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

Hi @mrj0b. Nice contribution, thank you. I’m not a maintainer of the project, but I ran into a similar issue and ended up here on your PR.

I left some suggestions about the changes you made. Take a look at them and let me know if they make sense to you, if you agree.

- LANGUAGE=${LANGUAGE}
- CONFIG_SESSION_PHONE_CLIENT=${CONFIG_SESSION_PHONE_CLIENT}
- CONFIG_SESSION_PHONE_NAME=${CONFIG_SESSION_PHONE_NAME}
- CONFIG_SESSION_PHONE_VERSION=${CONFIG_SESSION_PHONE_VERSION}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
- CONFIG_SESSION_PHONE_VERSION=${CONFIG_SESSION_PHONE_VERSION}

The variable CONFIG_SESSION_PHONE_VERSION no longer exists in the project.

The value used internally started being automatically populated in version v2.3.0.

It was completely removed in version v2.3.1.

"CONFIG_SESSION_PHONE_CLIENT=Evolution API",
"CONFIG_SESSION_PHONE_CLIENT=Evolution API V2",
"CONFIG_SESSION_PHONE_NAME=Chrome",
"CONFIG_SESSION_PHONE_VERSION=2.3000.1026420114",
Copy link
Copy Markdown
Contributor

@matheusfelipeog matheusfelipeog Oct 24, 2025

Choose a reason for hiding this comment

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

Suggested change
"CONFIG_SESSION_PHONE_VERSION=2.3000.1026420114",

Same as #review

"AUTHENTICATION_EXPOSE_IN_FETCH_INSTANCES=true",
"LANGUAGE=en",
"CONFIG_SESSION_PHONE_CLIENT=Evolution API",
"CONFIG_SESSION_PHONE_CLIENT=Evolution API V2",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
"CONFIG_SESSION_PHONE_CLIENT=Evolution API V2",
"CONFIG_SESSION_PHONE_CLIENT=Evolution API",

I don’t think this is necessary and it might cause some confusion. It would also require updating with every new major release.

What was originally there is fine and already makes clear what it refers to. The Evolution API version is also displayed next to the name in the interface.

Comment on lines +105 to +115
"OPENAI_ENABLED=true",
"DIFY_ENABLED=true",
"FLOWISE_ENABLED=true",
"N8N_ENABLED=true",
"TYPEBOT_ENABLED=true",
"TYPEBOT_API_VERSION=latest",
"CHATWOOT_ENABLED=true",
"CHATWOOT_MESSAGE_READ=true",
"CHATWOOT_MESSAGE_DELETE=true",
"CHATWOOT_IMPORT_DATABASE_CONNECTION_URI=chatwoot",
"CHATWOOT_IMPORT_PLACEHOLDER_MEDIA_MESSAGE=true",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
"OPENAI_ENABLED=true",
"DIFY_ENABLED=true",
"FLOWISE_ENABLED=true",
"N8N_ENABLED=true",
"TYPEBOT_ENABLED=true",
"TYPEBOT_API_VERSION=latest",
"CHATWOOT_ENABLED=true",
"CHATWOOT_MESSAGE_READ=true",
"CHATWOOT_MESSAGE_DELETE=true",
"CHATWOOT_IMPORT_DATABASE_CONNECTION_URI=chatwoot",
"CHATWOOT_IMPORT_PLACEHOLDER_MEDIA_MESSAGE=true",
"OPENAI_ENABLED=false",
"DIFY_ENABLED=false",
"FLOWISE_ENABLED=false",
"N8N_ENABLED=false",
"TYPEBOT_ENABLED=false",
"TYPEBOT_API_VERSION=latest",
"CHATWOOT_ENABLED=false",
"CHATWOOT_MESSAGE_READ=false",
"CHATWOOT_MESSAGE_DELETE=false",
"CHATWOOT_IMPORT_DATABASE_CONNECTION_URI=",
"CHATWOOT_IMPORT_PLACEHOLDER_MEDIA_MESSAGE=false",

I read the issues you opened and I understand your point. I don’t think it’s a good idea to set the variables that enable integrations with external platforms/resources to true by default --- especially since this is meant to serve as a template for others to use --- just like you didn’t enable RABBITMQ, SQS, WEBSOCKET, etc. by default. Not everyone will use the same features you do.

I suggest keeping the same default values provided by the Evolution API itself in the .env.example and env.example files. The template user should be responsible for enabling the features they need for their instance.

What do you think about that?


p.s. I haven’t checked all the variables you defined here, but the same idea applies to any others as well.


x-base-config: &base-config
image: chatwoot/chatwoot:v4.0.3
image: chatwoot/chatwoot:latest
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We shouldn't use latest images, this can break the templates easily

@Siumauricio Siumauricio changed the base branch from main to canary November 28, 2025 09:17
@russorat
Copy link
Copy Markdown
Collaborator

@mrj0b what do you think about the suggested changes?

@Siumauricio
Copy link
Copy Markdown
Contributor

Close due to inacitivty

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.

5 participants